Method and device for transmitting and receiving signal in wireless communication system

ABSTRACT

A terminal according to one embodiment of the present invention determines and reports a specific codebook-based HARQ-ACK on the basis of the result of receiving a plurality of PDSCHs, and, on the basis of a first-type codebook-based HARQ-ACK having been set for scheduling of the plurality of PDSCHs, the terminal can perform first start symbol and length indicator value (SLIV) pruning on the basis of a set of the SLIVs of PDSCHs, which can be potentially scheduled on each slot of a bundling window determined on the basis of a plurality of candidate PDSCH-to-HARQ feedback timing values, and perform second SLIV pruning on the basis of a set of the SLIVs of PDSCHs, which can be potentially scheduled even on at least one slot that does not belong to the bundling window.

TECHNICAL FIELD

The present disclosure relates to a wireless communication system, andmore particularly, to a method and apparatus for transmitting/receivingan uplink/downlink wireless signal in a wireless communication system.

BACKGROUND ART

Generally, a wireless communication system is developing to diverselycover a wide range to provide such a communication service as an audiocommunication service, a data communication service and the like. Thewireless communication is a sort of a multiple access system capable ofsupporting communications with multiple users by sharing availablesystem resources (e.g., bandwidth, transmit power, etc.). For example,the multiple access system may be any of a code division multiple access(CDMA) system, a frequency division multiple access (FDMA) system, atime division multiple access (TDMA) system, an orthogonal frequencydivision multiple access (OFDMA) system, and a single carrier frequencydivision multiple access (SC-FDMA) system.

DISCLOSURE Technical Problem

An object of the present disclosure is to provide a method ofefficiently performing wireless signal transmission/reception proceduresand an apparatus therefor.

It will be appreciated by persons skilled in the art that the objectsthat could be achieved with the present disclosure are not limited towhat has been particularly described hereinabove and the above and otherobjects that the present disclosure could achieve will be more clearlyunderstood from the following detailed description.

Technical Solution

According to an aspect of the present disclosure, a method of receivinga signal by a user equipment (UE) in a wireless communication system mayinclude receiving downlink control information (DCI) scheduling aplurality of physical downlink shared channels (PDSCHs), performingPDSCH reception for at least part of the plurality of PDSCHs based onthe DCI, determining a specific codebook-based hybrid automatic repeatrequest (HARQ)-acknowledgment (ACK), based on a result of the PDSCHreception, and transmitting the HARQ-ACK in slot #N related to aspecific candidate PDSCH-to-HARQ feedback timing value (K1 value)indicated by the DCI among a plurality of candidate K1 values configuredfor the UE.

In the determination of the HARQ-ACK, based on that a first-typecodebook-based HARQ-ACK is configured for the scheduling of theplurality of PDSCHs the UE may, perform first start symbol and lengthindicator value (SLIV) pruning based on a combination of SLIV values ofPDSCHs which can be potentially scheduled in each slot of a bundlingwindow determined based on the plurality of candidate K1 values, andperform second SLIV pruning based on a combination of SLIV values ofPDSCHs which can be potentially scheduled in at least one slot notbelonging to the bundling window.

The first ACK/negative-ACK (NACK) sub-payload for each slot of thebundling window may be determined based on the first SLIV pruning

Second ACK/NACK sub-payload for the at least one slot not belonging tothe bundling window may be determined based on the second SLIV pruning.

The UE may generate a total payload of the first-type codebook-basedHARQ-ACK by concatenating the first ACK/NACK sub-payload and the secondACK/NACK sub-payload, or arranging the first ACK/NACK sub-payload andthe second ACK/NACK sub-payload based on a time order of correspondingslots.

The at least one slot not belonging to the bundling window, for whichthe second SLIV pruning is performed, may be located before the bundlingwindow in a time domain.

The at least one slot not belonging to the bundling window, for whichthe second SLIV pruning is performed, may be a slot in which a PDSCHlocated outside the bundling window among the plurality of PDSCHs isreceived.

A time domain resource allocation (TDRA) field included in the DCI mayindicate one row of a TDRA table configured for the UE.

At least one row of the TDRA table may include a plurality of {K0, PDSCHmapping type, SLIV} parameter sets, where ‘K0’ may indicate a physicaldownlink control channel (PDCCH)-to-PDSCH slot offset.

The at least one slot not belonging to the bundling window, for whichthe second SLIV pruning is performed, may be determined based on ‘K0’included in a parameter set that does not correspond to a last slot ineach row of the TDRA table.

The bundling window for which the first SLIV pruning is performed may bedetermined by combining the plurality of candidate K1 values with aparameter set corresponding to the last slot in each row of the TDRAtable.

The HARQ-ACK may be generated for a valid PDSCH except for an invalidPDSCH overlapping with an uplink (UL) symbol configured by higher-layersignaling, among the plurality of PDSCHs.

The UE may perform each of the first SLIV pruning and the second SLIVpruning while excluding an invalid PDSCH overlapping with a UL symbolconfigured by higher-layer signaling.

According to an aspect of the present disclosure, a computer-readablerecording medium recording a program for performing the above signalreception method may be provided.

According to an aspect of the present disclosure, a UE for performingthe above signal reception method may be provided.

According to an aspect of the present disclosure, a device forcontrolling a UE for performing the above signal reception method may beprovided.

According to an aspect of the present disclosure, a method oftransmitting a signal by a BS in a wireless communication system mayinclude transmitting DCI scheduling a plurality of PDSCHs, performingPDSCH transmission for at least part of the plurality of PDSCHs based onthe DCI, receiving an HARQ-ACK in slot #N related to a specificcandidate PDSCH-to-HARQ feedback timing value (K1 value) indicated bythe DCI among a plurality of candidate K1 values configured for a UE,and determining a PDSCH to be retransmitted by processing the receivedHARQ-ACK.

In the determination of the PDSCH to be retransmitted, based on that afirst-type codebook-based HARQ-ACK is configured for the scheduling ofthe plurality of PDSCHs, the BS may perform first SLIV pruning based ona combination of SLIV values of PDSCHs which can be potentiallyscheduled in each slot of a bundling window determined based on theplurality of candidate K1 values, and perform second SLIV pruning basedon a combination of SLIV values of PDSCHs which can be potentiallyscheduled in at least one slot not belonging to the bundling window.

According to an aspect of the present disclosure, a BS for performingthe above signal reception method may be provided.

Advantageous Effects

According to the present disclosure, wireless signal transmission andreception may be efficiently performed in a wireless communicationsystem.

It will be appreciated by persons skilled in the art that the effectsthat can be achieved with the present disclosure are not limited to whathas been particularly described hereinabove and other advantages of thepresent disclosure will be more clearly understood from the followingdetailed description taken in conjunction with the accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the disclosure and are incorporated in and constitute apart of this application, illustrate embodiments of the disclosure andtogether with the description serve to explain the principle of thedisclosure. In the drawings:

FIG. 1 illustrates physical channels used in a 3rd generationpartnership project (3GPP) system as an exemplary wireless communicationsystem, and a general signal transmission method using the same;

FIG. 2 illustrates a radio frame structure;

FIG. 3 illustrates a resource grid of a slot;

FIG. 4 illustrates exemplary mapping of physical channels in a slot;

FIG. 5 illustrates an exemplary acknowledgment/negative acknowledgment(ACK/NACK) transmission process;

FIG. 6 illustrates an exemplary physical uplink shared channel (PUSCH)transmission process;

FIG. 7 illustrates an example of multiplexing control information in aPUSCH;

FIG. 8 illustrates hybrid automatic repeat request (HARQ)-processidentifier (ID) allocation for multi-transmission time interval (TTI)scheduling according to an embodiment of the present disclosure;

FIG. 9 illustrates start and length indicator value (SLIV) pruning formulti-TTI scheduling according to an embodiment of the presentdisclosure;

FIG. 10 illustrates multi-physical downlink shared channel (PDSCH)scheduling and HARQ-ACK reporting according to an embodiment of thepresent disclosure;

FIG. 11 illustrates multi-TTI PUSCH transmission/reception and HARQ-ACKreception according to an embodiment of the present disclosure;

FIGS. 12 and 13 illustrate signal transmission and reception methods,respectively according to an embodiment of the present disclosure;

FIGS. 14 to 17 illustrate an example of a communication system 1 andwireless devices applied to the present disclosure; and

FIG. 18 illustrates an exemplary discontinuous reception (DRX) operationapplicable to the present disclosure.

MODE FOR INVENTION

Embodiments of the present disclosure are applicable to a variety ofwireless access technologies such as code division multiple access(CDMA), frequency division multiple access (FDMA), time divisionmultiple access (TDMA), orthogonal frequency division multiple access(OFDMA), and single carrier frequency division multiple access(SC-FDMA). CDMA can be implemented as a radio technology such asUniversal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can beimplemented as a radio technology such as Global System for Mobilecommunications (GSM)/General Packet Radio Service (GPRS)/Enhanced DataRates for GSM Evolution (EDGE). OFDMA can be implemented as a radiotechnology such as Institute of Electrical and Electronics Engineers(IEEE) 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Worldwideinteroperability for Microwave Access (WiMAX)), IEEE 802.20, and EvolvedUTRA (E-UTRA). UTRA is a part of Universal Mobile TelecommunicationsSystem (UMTS). 3rd Generation Partnership Project (3GPP) Long TermEvolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA, andLTE-Advanced (A) is an evolved version of 3GPP LTE. 3GPP NR (New Radioor New Radio Access Technology) is an evolved version of 3GPP LTE/LTE-A.

As more and more communication devices require a larger communicationcapacity, there is a need for mobile broadband communication enhancedover conventional radio access technology (RAT). In addition, massiveMachine Type Communications (MTC) capable of providing a variety ofservices anywhere and anytime by connecting multiple devices and objectsis another important issue to be considered for next generationcommunications. Communication system design considering services/UEssensitive to reliability and latency is also under discussion. As such,introduction of new radio access technology considering enhanced mobilebroadband communication (eMBB), massive MTC, and Ultra-Reliable and LowLatency Communication (URLLC) is being discussed. In the presentdisclosure, for simplicity, this technology will be referred to as NR(New Radio or New RAT).

For the sake of clarity, 3GPP NR is mainly described, but the technicalidea of the present disclosure is not limited thereto.

In the present disclosure, the term “set/setting” may be replaced with“configure/configuration”, and both may be used interchangeably.Further, a conditional expression (e.g., “if”, “in a case”, or “when”)may be replaced by “based on that” or “in a state/status”. In addition,an operation or software/hardware (SW/HW) configuration of a userequipment (UE)/base station (BS) may be derived/understood based onsatisfaction of a corresponding condition. When a process on a receiving(or transmitting) side may be derived/understood from a process on thetransmitting (or receiving) side in signal transmission/receptionbetween wireless communication devices (e.g., a BS and a UE), itsdescription may be omitted. Signaldetermination/generation/encoding/transmission of the transmitting side,for example, may be understood as signal monitoringreception/decoding/determination of the receiving side. Further, when itis said that a UE performs (or does not perform) a specific operation,this may also be interpreted as that a BS expects/assumes (or does notexpect/assume) that the UE performs the specific operation. When it issaid that a BS performs (or does not perform) a specific operation, thismay also be interpreted as that a UE expects/assumes (or does notexpect/assume) that the BS performs the specific operation. In thefollowing description, sections, embodiments, examples, options,methods, schemes, and so on are distinguished from each other andindexed, for convenience of description, which does not mean that eachof them necessarily constitutes an independent invention or that each ofthem should be implemented only individually. Unless explicitlycontradicting each other, it may be derived/understood that at leastpart of the sections, embodiments, examples, options, methods, schemes,and so on may be implemented in combination or may be omitted.

In a wireless communication system, a user equipment (UE) receivesinformation through downlink (DL) from a base station (BS) and transmitinformation to the BS through uplink (UL). The information transmittedand received by the BS and the UE includes data and various controlinformation and includes various physical channels according totype/usage of the information transmitted and received by the UE and theBS.

FIG. 1 illustrates physical channels used in a 3GPP NR system and ageneral signal transmission method using the same.

When a UE is powered on again from a power-off state or enters a newcell, the UE performs an initial cell search procedure, such asestablishment of synchronization with a BS, in step S101. To this end,the UE receives a synchronization signal block (SSB) from the BS. TheSSB includes a primary synchronization signal (PSS), a secondarysynchronization signal (SSS), and a physical broadcast channel (PBCH).The UE establishes synchronization with the BS based on the PSS/SSS andacquires information such as a cell identity (ID). The UE may acquirebroadcast information in a cell based on the PBCH. The UE may receive aDL reference signal (RS) in an initial cell search procedure to monitora DL channel status.

After initial cell search, the UE may acquire more specific systeminformation by receiving a physical downlink control channel (PDCCH) andreceiving a physical downlink shared channel (PDSCH) based oninformation of the PDCCH in step S102.

The UE may perform a random access procedure to access the BS in stepsS103 to S106. For random access, the UE may transmit a preamble to theBS on a physical random access channel (PRACH) (S103) and receive aresponse message for preamble on a PDCCH and a PDSCH corresponding tothe PDCCH (S104). In the case of contention-based random access, the UEmay perform a contention resolution procedure by further transmittingthe PRACH (S105) and receiving a PDCCH and a PDSCH corresponding to thePDCCH (S106).

After the foregoing procedure, the UE may receive a PDCCH/PDSCH (S107)and transmit a physical uplink shared channel (PUSCH)/physical uplinkcontrol channel (PUCCH) (S108), as a general downlink/uplink signaltransmission procedure. Control information transmitted from the UE tothe BS is referred to as uplink control information (UCI). The UCIincludes hybrid automatic repeat and requestacknowledgement/negative-acknowledgement (HARQ-ACK/NACK), schedulingrequest (SR), channel state information (CSI), etc. The CSI includes achannel quality indicator (CQI), a precoding matrix indicator (PMI), arank indicator (RI), etc. While the UCI is transmitted on a PUCCH ingeneral, the UCI may be transmitted on a PUSCH when control informationand traffic data need to be simultaneously transmitted. In addition, theUCI may be aperiodically transmitted through a PUSCH according torequest/command of a network.

FIG. 2 illustrates a radio frame structure. In NR, uplink and downlinktransmissions are configured with frames. Each radio frame has a lengthof 10 ms and is divided into two 5-ms half-frames (HF). Each half-frameis divided into five 1-ms subframes (SFs). A subframe is divided intoone or more slots, and the number of slots in a subframe depends onsubcarrier spacing (SCS). Each slot includes 12 or 14 OrthogonalFrequency Division Multiplexing (OFDM) symbols according to a cyclicprefix (CP). When a normal CP is used, each slot includes 14 OFDMsymbols. When an extended CP is used, each slot includes 12 OFDMsymbols.

Table 1 exemplarily shows that the number of symbols per slot, thenumber of slots per frame, and the number of slots per subframe varyaccording to the SCS when the normal CP is used.

TABLE 1 SCS (15*2^(u)) N^(slot) _(symb) N^(frame, u) _(slot)N^(subframe, u) _(slot) 15 KHz (u = 0) 14 10 1 30 KHz (u = 1) 14 20 2 60KHz (u = 2) 14 40 4 120 KHz (u = 3) 14 80 8 240 KHz (u = 4) 14 160 16N^(slot) _(symb): Number of symbols in a slot N^(frame, u) _(slot):Number of slots in a frame N^(subframe, u) _(slot): Number of slots in asubframe

Table 2 illustrates that the number of symbols per slot, the number ofslots per frame, and the number of slots per subframe vary according tothe SCS when the extended CP is used.

TABLE 2 SCS (15*2^(u)) N^(slot) _(symb) N^(frame, u) _(slot)N^(subframe, u) _(slot) 60 KHz (u = 2) 12 40 4

The structure of the frame is merely an example. The number ofsubframes, the number of slots, and the number of symbols in a frame mayvary.

In the NR system, OFDM numerology (e.g., SCS) may be configureddifferently for a plurality of cells aggregated for one UE. Accordingly,the (absolute time) duration of a time resource (e.g., an SF, a slot ora TTI) (for simplicity, referred to as a time unit (TU)) consisting ofthe same number of symbols may be configured differently among theaggregated cells. Here, the symbols may include an OFDM symbol (or aCP-OFDM symbol) and an SC-FDMA symbol (or a discrete Fouriertransform-spread-OFDM (DFT-s-OFDM) symbol).

FIG. 3 illustrates a resource grid of a slot. A slot includes aplurality of symbols in the time domain. For example, when the normal CPis used, the slot includes 14 symbols. However, when the extended CP isused, the slot includes 12 symbols. A carrier includes a plurality ofsubcarriers in the frequency domain. A resource block (RB) is defined asa plurality of consecutive subcarriers (e.g., 12 consecutivesubcarriers) in the frequency domain. A bandwidth part (BWP) may bedefined to be a plurality of consecutive physical RBs (PRBs) in thefrequency domain and correspond to a single numerology (e.g., SCS, CPlength, etc.). The carrier may include up to N (e.g., 5) BWPs. Datacommunication may be performed through an activated BWP, and only oneBWP may be activated for one UE. In the resource grid, each element isreferred to as a resource element (RE), and one complex symbol may bemapped to each RE.

FIG. 4 illustrates exemplary mapping of physical channels in a slot. APDCCH may be transmitted in a DL control region, and a PDSCH may betransmitted in a DL data region. A PUCCH may be transmitted in a ULcontrol region, and a PUSCH may be transmitted in a UL data region. Aguard period (GP) provides a time gap for transmission mode-to-receptionmode switching or reception mode-to-transmission mode switching at a BSand a UE. Some symbol at the time of DL-to-UL switching in a subframemay be configured as a GP.

Each physical channel will be described below in greater detail.

The PDCCH delivers DCI. For example, the PDCCH (i.e., DCI) may carryinformation about a transport format and resource allocation of a DLshared channel (DL-SCH), resource allocation information of an uplinkshared channel (UL-SCH), paging information on a paging channel (PCH),system information on the DL-SCH, information on resource allocation ofa higher-layer control message such as an RAR transmitted on a PDSCH, atransmit power control command, information about activation/release ofconfigured scheduling, and so on. The DCI includes a cyclic redundancycheck (CRC). The CRC is masked with various identifiers (IDs) (e.g. aradio network temporary identifier (RNTI)) according to an owner orusage of the PDCCH. For example, if the PDCCH is for a specific UE, theCRC is masked by a UE ID (e.g., cell-RNTI (C-RNTI)). If the PDCCH is fora paging message, the CRC is masked by a paging-RNTI (P-RNTI). If thePDCCH is for system information (e.g., a system information block(SIB)), the CRC is masked by a system information RNTI (SI-RNTI). Whenthe PDCCH is for an RAR, the CRC is masked by a random access-RNTI(RA-RNTI).

The PDCCH includes 1, 2, 4, 8, or 16 control channel elements (CCEs)according to its aggregation level (AL). A CCE is a logical allocationunit used to provide a PDCCH with a specific code rate according to aradio channel state. A CCE includes 6 resource element groups (REGs),each REG being defined by one OFDM symbol by one (P)RB. The PDCCH istransmitted in a control resource set (CORESET). A CORESET is defined asa set of REGs with a given numerology (e.g., an SCS, a CP length, and soon). A plurality of CORESETs for one UE may overlap with each other inthe time/frequency domain. A CORESET may be configured by systeminformation (e.g., a master information block (MIB)) or UE-specifichigher-layer signaling (e.g., radio resource control (RRC) signaling).Specifically, the number of RBs and the number of symbols (3 at maximum)in the CORESET may be configured by higher-layer signaling.

For PDCCH reception/detection, the UE monitors PDCCH candidates. A PDCCHcandidate is CCE(s) that the UE should monitor to detect a PDCCH. EachPDCCH candidate is defined as 1, 2, 4, 8, or 16 CCEs according to an AL.The monitoring includes (blind) decoding PDCCH candidates. A set ofPDCCH candidates decoded by the UE are defined as a PDCCH search space(SS). An SS may be a common search space (CSS) or a UE-specific searchspace (USS). The UE may obtain DCI by monitoring PDCCH candidates in oneor more SSs configured by an MIB or higher-layer signaling. Each CORESETis associated with one or more SSs, and each SS is associated with oneCORESET. An SS may be defined based on the following parameters.

controlResourceSetId: A CORESET related to an SS.

monitoringSlotPeriodicityAndOffset: A PDCCH monitoring periodicity (inslots) and a PDCCH monitoring offset (in slots).

monitoringSymbolsWithinSlot: PDCCH monitoring symbols in a slot (e.g.,the first symbol(s) of a CORESET).

nrofCandidates: The number of PDCCH candidates (one of 0, 1, 2, 3, 4, 5,6, and 8) for each AL={1, 2, 4, 8, 16}.

An occasion (e.g., time/frequency resources) in which the UE is tomonitor PDCCH candidates is defined as a PDCCH (monitoring) occasion.One or more PDCCH (monitoring) occasions may be configured in a slot.

Table 3 shows the characteristics of each SS.

TABLE 3 Search Type Space RNTI Use Case Type0- Common SI-RNTI on aprimary cell SIB PDCCH Decoding Type0A- Common SI-RNTI on a primary cellSIB PDCCH Decoding Type1- Common RA-RNTI or TC-RNTI on a Msg2, Msg4PDCCH primary cell decoding in RACH Type2- Common P-RNTI on a primarycell Paging PDCCH Decoding Type3- Common INT-RNTI, SFI-RNTI, TPC- PDCCHPUSCH-RNTI, TPC-PUCCH- RNTI, TPC-SRS-RNTI, C- RNTI, MCS-C-RNTI, or CS-RNTI(s) UE C-RNTI, or MCS-C-RNTI, or User specific Specific CS-RNTI(s)PDSCH decoding

Table 4 shows DCI formats transmitted on the PDCCH.

TABLE 4 DCI format Usage 0_0 Scheduling of PUSCH in one cell 0_1Scheduling of PUSCH in one cell 1_0 Scheduling of PDSCH in one cell 1_1Scheduling of PDSCH in one cell 2_0 Notifying a group of UEs of the slotformat 2_1 Notifying a group of UEs of the PRB(s) and OFDM symbol(s)where UE may assume no transmission is intended for the UE 2_2Transmission of TPC commands for PUCCH and PUSCH 2_3 Transmission of agroup of TPC commands for SRS transmissions by one or more UEs

DCI format 0_0 may be used to schedule a TB-based (or TB-level) PUSCH,and DCI format 0_1 may be used to schedule a TB-based (or TB-level)PUSCH or a code block group (CBG)-based (or CBG-level) PUSCH. DCI format1_0 may be used to schedule a TB-based (or TB-level) PDSCH, and DCIformat 1_1 may be used to schedule a TB-based (or TB-level) PDSCH or aCBG-based (or CBG-level) PDSCH (DL grant DCI). DCI format 0_0/0_1 may bereferred to as UL grant DCI or UL scheduling information, and DCI format1_0/1_1 may be referred to as DL grant DCI or DL scheduling information.DCI format 2_0 is used to deliver dynamic slot format information (e.g.,a dynamic slot format indicator (SFI)) to a UE, and DCI format 2_1 isused to deliver DL pre-emption information to a UE. DCI format 2_0and/or DCI format 2_1 may be delivered to a corresponding group of UEson a group common PDCCH which is a PDCCH directed to a group of UEs.

DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCIformats, whereas DCI format 0_1 and DCI format 1_1 may be referred to asnon-fallback DCI formats. In the fallback DCI formats, a DCI size/fieldconfiguration is maintained to be the same irrespective of a UEconfiguration. In contrast, the DCI size/field configuration variesdepending on a UE configuration in the non-fallback DCI formats.

The PDSCH conveys DL data (e.g., DL-shared channel transport block(DL-SCH TB)) and uses a modulation scheme such as quadrature phase shiftkeying (QPSK), 16-ary quadrature amplitude modulation (16QAM), 64QAM, or256QAM. A TB is encoded into a codeword. The PDSCH may deliver up to twocodewords. Scrambling and modulation mapping may be performed on acodeword basis, and modulation symbols generated from each codeword maybe mapped to one or more layers. Each layer together with a demodulationreference signal (DMRS) is mapped to resources, and an OFDM symbolsignal is generated from the mapped layer with the DMRS and transmittedthrough a corresponding antenna port.

System information (SIB1) broadcast in a cell includes cell-specificPDSCH configuration information, PDSCH-ConfigCommon. PDSCH-ConfigCommonincludes a list of parameters (or a look-up table) related to atime-domain resource allocation for a PDSCH,pdsch-TimeDomainAllocationList. pdsch-TimeDomainAllocationList mayinclude up to 16 entries (or rows) each having {K0, PDSCH mapping type,PDSCH start symbol and length (SLIV)} which are jointly encoded. Asidefrom (additionally to) pdsch-TimeDomainAllocationList configured byPDSCH-ConfigCommon, pdsch-TimeDomainAllocationList may also be providedby a UE-specific PDSCH configuration, PDSCH-Config. UE-specificallyconfigured pdsch-TimeDomainAllocationList may have the same structure asUE-commonly configured pdsch-TimeDomainAllocationList. For K0 and SLIVof pdsch-TimeDomainAllocationList, the following description includingthat of FIG. 5 may be referred to.

DL data packet (e.g., codeword) on the PDSCH. An HARQ-ACK indicateswhether the DL data packet has been successfully received. In responseto a single codeword, a 1-bit of HARQ-ACK may be transmitted. Inresponse to two codewords, a 2-bit HARQ-ACK may be transmitted. TheHARQ-ACK response includes positive ACK (simply, ACK), negative ACK(NACK), discontinuous transmission (DTX) or NACK/DTX. The term HARQ-ACKis interchangeably used with HARQ ACK/NACK and ACK/NACK.

CSI (Channel State Information): Feedback information for a DL channel.Multiple input multiple output (MIMO)-related feedback informationincludes an RI and a PMI.

Table 5 illustrates exemplary PUCCH formats. PUCCH formats may bedivided into short PUCCHs (Formats 0 and 2) and long PUCCHs (Formats 1,3, and 4) based on PUCCH transmission durations.

TABLE 5 Length in PUCCH OFDM symbols Number of format N_(symb) ^(PUCCH)bits Usage Etc 0 1-2  ≤2 HARQ, SR Sequence selection 1 4-14 ≤2 HARQ,[SR] Sequence modulation 2 1-2  >2 HARQ, CSI, CP-OFDM [SR] 3 4-14 >2HARQ, CSI, DFT-s-OFDM [SR] (no UE multiplexing) 4 4-14 >2 HARQ, CSI,DFT-s-OFDM [SR] (Pre DFT OCC)

PUCCH format 0 conveys UCI of up to 2 bits and is mapped in asequence-based manner, for transmission. Specifically, the UE transmitsspecific UCI to the BS by transmitting one of a plurality of sequenceson a PUCCH of PUCCH format 0. Only when the UE transmits a positive SR,the UE transmits the PUCCH of PUCCH format 0 in PUCCH resources for acorresponding SR configuration.

PUCCH format 1 conveys UCI of up to 2 bits and modulation symbols of theUCI are spread with an orthogonal cover code (OCC) (which is configureddifferently whether frequency hopping is performed) in the time domain.The DMRS is transmitted in a symbol in which a modulation symbol is nottransmitted (i.e., transmitted in time division multiplexing (TDM)).

PUCCH format 2 conveys UCI of more than 2 bits and modulation symbols ofthe DCI are transmitted in frequency division multiplexing (FDM) withthe DMRS. The DMRS is located in symbols #1, #4, #7, and #10 of a givenRB with a density of 1/3. A pseudo noise (PN) sequence is used for aDMRS sequence. For 2-symbol PUCCH format 2, frequency hopping may beactivated.

PUCCH format 3 does not support UE multiplexing in the same PRBS, andconveys UCI of more than 2 bits. In other words, PUCCH resources ofPUCCH format 3 do not include an OCC. Modulation symbols are transmittedin TDM with the DMRS.

PUCCH format 4 supports multiplexing of up to 4 UEs in the same PRBS,and conveys UCI of more than 2 bits. In other words, PUCCH resources ofPUCCH format 3 include an OCC. Modulation symbols are transmitted in TDMwith the DMRS.

The PUSCH delivers UL data (e.g., UL-shared channel transport block(UL-SCH TB)) and/or UCI based on a CP-OFDM waveform or a DFT-s-OFDMwaveform. When the PUSCH is transmitted in the DFT-s-OFDM waveform, theUE transmits the PUSCH by transform precoding. For example, whentransform precoding is impossible (e.g., disabled), the UE may transmitthe PUSCH in the CP-OFDM waveform, while when transform precoding ispossible (e.g., enabled), the UE may transmit the PUSCH in the CP-OFDMor DFT-s-OFDM waveform. A PUSCH transmission may be dynamicallyscheduled by a UL grant in DCI, or semi-statically scheduled byhigher-layer (e.g., RRC) signaling (and/or Layer 1 (L1) signaling suchas a PDCCH) (configured scheduling or configured grant). The PUSCHtransmission may be performed in a codebook-based or non-codebook-basedmanner.

FIG. 5 illustrates an exemplary PDSCH reception and ACK/NACKtransmission process. Referring to FIG. 5 , the UE may detect a PDCCH inslot #n. The PDCCH includes DL scheduling information (e.g., DCI format1_0 or DCI format 1_1). The PDCCH indicates a DL assignment-to-PDSCHoffset, K0 and a PDSCH-to-HARQ-ACK reporting offset, K1. For example,DCI format 1_0 and DCI format 1_1 may include the following information.

Frequency domain resource assignment: Indicates an RB set assigned to aPDSCH.

Time domain resource assignment: Indicates K0 and the starting position(e.g. OFDM symbol index) and length (e.g. the number of OFDM symbols) ofthe PDSCH in a slot. As described above, a row index ofpdsch-TimeDomainAllocationList provided UE-commonly or UE-specificallymay be indicated by a TDRA field.

PDSCH-to-HARQ_feedback timing indicator: Indicates K1.

HARQ process number (4 bits): Indicates the HARQ process ID of data(e.g., a PDSCH or TB).

PUCCH resource indicator (PRI): Indicates a PUCCH resource to be usedfor UCI transmission among a plurality of PUCCH resources in a PUCCHresource set.

After receiving a PDSCH in slot #(n+K0) according to the schedulinginformation of slot #n, the UE may transmit UCI on a PUCCH in slot#(n+K1). The UCI may include an HARQ-ACK response to the PDSCH. FIG. 5is based on the assumption that the SCS of the PDSCH is equal to the SCSof the PUCCH, and slot #n1=slot #(n+K0), for convenience, which shouldnot be construed as limiting the present disclosure. When the SCSs aredifferent, K1 may be indicated/interpreted based on the SCS of thePUCCH.

In the case where the PDSCH is configured to carry one TB at maximum,the HARQ-ACK response may be configured in one bit. In the case wherethe PDSCH is configured to carry up to two TBs, the HARQ-ACK responsemay be configured in 2 bits if spatial bundling is not configured and in1 bit if spatial bundling is configured. When slot #(n+K1) is designatedas an HARQ-ACK transmission timing for a plurality of PDSCHs, UCItransmitted in slot #(n+K1) includes HARQ-ACK responses to the pluralityof PDSCHs.

Whether the UE should perform spatial bundling for an HARQ-ACK responsemay be configured for each cell group (e.g., by RRC/higher layersignaling). For example, spatial bundling may be configured for eachindividual HARQ-ACK response transmitted on the PUCCH and/or HARQ-ACKresponse transmitted on the PUSCH.

When up to two (or two or more) TBs (or codewords) may be received atone time (or schedulable by one DCI) in a corresponding serving cell(e.g., when a higher layer parameter maxNrofCodeWordsScheduledByDCIindicates 2 TBs), spatial bundling may be supported. More than fourlayers may be used for a 2-TB transmission, and up to four layers may beused for a 1-TB transmission. As a result, when spatial bundling isconfigured for a corresponding cell group, spatial bundling may beperformed for a serving cell in which more than four layers may bescheduled among serving cells of the cell group. A UE which wants totransmit an HARQ-ACK response through spatial bundling may generate anHARQ-ACK response by performing a (bit-wise) logical AND operation onA/N bits for a plurality of TBs.

For example, on the assumption that the UE receives DCI scheduling twoTBs and receives two TBs on a PDSCH based on the DCI, a UE that performsspatial bundling may generate a single A/N bit by a logical ANDoperation between a first A/N bit for a first TB and a second A/N bitfor a second TB. As a result, when both the first TB and the second TBare ACKs, the UE reports an ACK bit value to a BS, and when at least oneof the TBs is a NACK, the UE reports a NACK bit value to the BS.

For example, when only one TB is actually scheduled in a serving cellconfigured for reception of two TBs, the UE may generate a single A/Nbit by performing a logical AND operation on an A/N bit for the one TBand a bit value of 1. As a result, the UE reports the A/N bit for theone TB to the BS.

There are plurality of parallel DL HARQ processes for DL transmissionsat the BS/UE. The plurality of parallel HARQ processes enable continuousDL transmissions, while the BS is waiting for an HARQ feedbackindicating successful or failed reception of a previous DL transmission.Each HARQ process is associated with an HARQ buffer in the medium accesscontrol (MAC) layer. Each DL HARQ process manages state variables suchas the number of MAC physical data unit (PDU) transmissions, an HARQfeedback for a MAC PDU in a buffer, and a current redundancy version.Each HARQ process is identified by an HARQ process ID.

FIG. 6 illustrates an exemplary PUSCH transmission procedure. Referringto FIG. 6 , the UE may detect a PDCCH in slot #n. The PDCCH includes DLscheduling information (e.g., DCI format 1_0 or 1_1). DCI format 1_0 or1_1 may include the following information.

Frequency domain resource assignment: Indicates an RB set assigned tothe PUSCH.

Time domain resource assignment: Indicates a slot offset K2 and thestarting position (e.g. OFDM symbol index) and duration (e.g. the numberof OFDM symbols) of the PUSCH in a slot. The starting symbol and lengthof the PUSCH may be indicated by a start and length indicator value(SLIV).

The UE may then transmit a PUSCH in slot #(n+K2) according to thescheduling information in slot #n. The PUSCH includes a UL-SCH TB.

FIG. 7 illustrates exemplary multiplexing of UCI in a PUSCH. When aplurality of PUCCH resources overlap with a PUSCH resource in a slot anda PUCCH-PUSCH simultaneous transmission is not configured in the slot,UCI may be transmitted on a PUSCH (UCI piggyback or PUSCH piggyback), asillustrated. In the illustrated case of FIG. 7 , an HARQ-ACK and CSI arecarried in a PUSCH resource.

In an NR Rel. 15/16 system, three HARQ-ACK codebook types are defineddepending on how an HARQ-ACK bit (payload) is configured: Type 1, Type2, and Type 3. In the Type-1 codebook, HARQ-ACK payload is configuredaccording to a combination of a candidate HARQ-ACK timing (K1) set and acandidate PDSCH occasion (SLIV) set (configured for a corresponding cellon a cell basis) (e.g., a codebook of a semi-static fixed length basedon RRC signaling). In a Type-2 codebook, a codebook size may be changeddynamically according to the number of actually scheduled PDSCHs or thenumber (e.g., DAI) of corresponding resource allocations. In a Type-3codebook, HARQ-ACK payload is configured by mapping an HARQ-ACK bit to acorresponding HARQ process number (HPN) on an HPN basis according to themaximum number of HARQ processes (configured for a corresponding cell ona cell basis) (e.g., one shot AN reporting)

Multi-TTI Scheduling and HARQ-ACK Feedback Based on Single DCI

The 3GPP (e.g., Rel-15 and Rel-16) has recently worked onstandardization of a 5G system called new RAT (NR). The NR system seeksto support a plurality of logical networks in a single physical system.For this purpose, the NR system is designed to support services (e.g.,eMBB, mMTC, and URLLC) having various requirements byperforming/modifying an analog/hybrid beamforming operation or the likein consideration of various OFDM numerologies (e.g., OFDM symboldurations, subcarrier spacings (SCSs), and CP lengths), a wide operatingfrequency range (up to about 50 GHz), and characteristics of a highfrequency band.

In Rel-17, a need for developing an NR (i.e., high frequency (HF) NR)system operating in a high frequency band (e.g., at or above 60 to 70GHz) higher than in the legacy Rel-15/16-based NR system is considered.In consideration of a higher frequency and wider bandwidth than in thelegacy NR, and radio channel characteristics such as a larger phasenoise and/or larger Doppler shift caused by the high frequency band,introduction and application of a new OFDM numerology based on a largerSCS (e.g., 240 KHz, 480 KHz, or 960 KHz) than the SCSs of legacy NR(e.g. the numerology defined in 3GPP TS 38.211, such as 15 KHz, 30 KHz,60 KHz, and 120 KHz) may be considered.

When a large SCS is used in the HF NR system, the OFDM symbol durationand the slot duration are shortened as much (e.g., when the SCSincreases by N times in the frequency domain, the symbol duration and/orthe slot duration decreases to 1/N in the time domain). Accordingly, acell plan to reduce cell coverage as much may be considered. However,otherwise (e.g., when (target) cell coverage is maintained to correspondto a legacy NR level or when the SCS of a system increases from a legacyNR SCS to a large SCS for HF NR, but the (target) cell coverage is notreduced, in inverse proportion to an SCS increase), there may be a needfor supplementing the coverage for physical channel/signal transmission(e.g., a scheme that extends/supplements coverage in processing aphysical channel/signal, so that a DL physical channel/signal may reacha UE at an edge/boundary of the target cell coverage or a UL physicalchannel/signal transmitted from the UE located at the edge/boundary ofthe target cell coverage reaches a BS). In addition, because the use ofa large SCS decreases a CP length as much, it is necessary to considerthe effect of the delay spread and/or phase noise of a radio channel,and/or a beam switching time.

The term “beam” may be replaced with (beamformed)signal/channel/resource transmitted through a corresponding beam. Forexample, the index of a beam may be generally expressed as the index ofa signal/channel/resource corresponding to the beam. Alternatively, theterm “beam” may be replaced with signal/channel/resource that isassociated with a beam and thus identifies the beam. When a different Txbeam is configured for each RO, the BS may identify a TX Beam used bythe UE through an RO index or SSB index associated with the RO.

Further, when the OFDM symbol and slot durations are reduced due to theuse of a large SCS as described above, a transmission/receptionoperation (e.g., PDCCH monitoring) that the UE is to be performed in onesymbol/slot duration requires fast processing, and in consideration of aUE processing burden (related to a PDCCH monitoring period), theintroduction of a multi-TTI scheduling scheme may be considered, whichsimultaneously schedules a plurality of multiplexed PDSCHs (e.g., atleast part of the PDSCHs are TDMed) by one DCI.

Accordingly, the present disclosure proposes a method of configuring andsignaling/applying multi-TTI (scheduling) DCI field information forsimultaneously scheduling multiple PDSCHs (and/or multiple PUSCHs) (eachcarrying one or more individual TBs), and a method of configuring anHARQ-ACK (i.e., A/N) feedback related to reception of multiple PDSCHsscheduled by the DCI. For example, a frequency band available forscheduling multiple PDSCHs by one DL DCI may include, but not limitedto, 120 KHz, 480 kHz, and/or 960 kHz.

While the present disclosure is described in the context of DL grantDCI-based multi-PDSCH scheduling, for convenience of description, thoseskilled in the art will understand that multi-TTI scheduling is alsoapplied to UL grant DCI-based multi-PUSCH scheduling, not limited to DLgrant DCI-based multi-PDSCH scheduling. In other words, the termmulti-TTI scheduling may be understood as covering both DL DCI thatschedules a plurality of PDSCHs multiplexed in the time domain and ULDCI that schedules a plurality of PUSCHs multiplexed in the time domain.

The meanings of terms as used herein are summarized as follows. To helpthe understanding of the terms, FIG. 5 /6 and its description may bereferred to.

K0 (DL assignment-to-PDSCH offset): A slot interval between a DCItransmission slot and a PDSCH transmission slot (scheduled bycorresponding DCI).

SLIV (Start and Length Indicator Value): Information about the startingsymbol and symbol duration (or ending symbol) of a PDSCH (PDSCHoccasion).

Mapping type: Information indicating whether the position of a DMRSsymbol of a PDSCH is determined based on a symbol index within a slotduration or within a PDSCH duration.

TDRA (Time Domain Resource Assignment) table: Includes a plurality of{K0, SLIV, mapping type} combinations (configured by RRC) (onecombination is mapped to each of a plurality of rows in the table). Aspecific one row is indicated by DCI.

K1 (PDSCH-to-HARQ_feedback timing indicator): A slot interval between aPDSCH transmission slot and an HARQ-ACK transmission slot (for acorresponding PDSCH reception).

(Proposal 1) Configuration of PDSCH Resource Allocation Field

(Proposal 1-A) Configuration of Time-Domain RA (TDRA) Field Information

The TDRA field of DL grant DCI may schedule multiple PDSCHs or the TDRAfield of UL grant DCI may schedule multiple PUSCHs.

1) Opt 1

A. For each state indicated by the TDRA field of multi-TTI DCI, Nentries may be configured based on a (higher-layer signaled) entrycomposed of {K0, SLIV, mapping type}. N is the number of scheduledPDSCHs, and may have a different value for each TDRA field state (e.g.,N>=1). For example, one TDRA field state may be mapped to N entriesbased on higher-layer signaling, and N PDSCHs may be allocated toconsecutive/non-consecutive slots. Those skilled in the art willunderstand that for a PUSCH, K2 may be provided instead of K0.

2) Opt 2

A. For each state indicated by the TDRA field of multi-TTI DCI, Nentries may be configured in the form of {K0, SLIV, mapping type} forthe first PDSCH (corresponding to the first entry (index)) and {D, SLIV,mapping type} for the following PDSCHs. D configured for an n^(th) PDSCHmay be applied as a slot interval between a previous (n-1)^(th) PDSCHtransmission slot and an n^(th) PDSCH transmission slot.

3) Opt 3

A. For each state indicated by the TDRA field of multi-TTI DCI, one K0value and N entries each including {SLIV, mapping type} may beconfigured. K0 may be applied to the first PDSCH (corresponding to thefirst entry (index)), and the following PDSCHs may be sequentiallytransmitted in consecutive slots (each for one PDSCH) (following thetransmission slot of the first PDSCH).

4) Opt 4

A. For each state indicated by the TDRA field of multi-TTI DCI, one K0value, one D value, and N entries each including {SLIV, mapping type}may be configured. K0 may be applied to the first PDSCH (correspondingto the first entry (index)), and the D value may be applied commonly tothe following PDSCHs.

(Proposal 1-B) Configuration of Frequency-Domain RA (FDRA) FieldInformation

1) Opt 1

A. The size of an RBG which is a resource allocation unit for RBG-basedFDRA, and the size of a related FDRA field may be determined/setaccording to the number of PDSCHs scheduled by multi-TTI DCI.

i. For example, when the number of scheduled PDSCHs is equal to or lessthan M, the legacy RBG size (e.g., X RBs) and the legacy FDRA field sizeare maintained. On the contrary, when the number of scheduled PDSCHs islarger than M, the RBG size is larger than the legacy size, X RBs, andthus the FDRA field size may be decreased. (In this case,characteristically M=1).

2) Opt 2

A. A resource granularity for RIV-based FDRA, and the size of a relatedFDRA field may be determined/set according to the number of PDSCHsscheduled by mufti-TTI DCI.

i. For example, when the number of scheduled PDSCHs is equal to or lessthan M, the legacy RIV method with a 1-RB granularity and the legacyFDRA field size are maintained. On the contrary, when the number ofscheduled PDSCHs is larger than M, an RIV method based on a K-RB (K>1)granularity may be used, and thus the FDRA field size may be decreased.(In this case, characteristically M=1).

(Proposal 2) Rate-Matching Indicator (RMI) Field Information

1) Opt 1

A. Rate-matching (pattern) information indicated by an RMI field ofmulti-TTI DCI may be applied commonly to a plurality of PDSCHs scheduledby the DCI. For example, the DCI may include one RMI field appliedcommonly to a plurality of PDSCHs.

2) Opt 2

A. Rate-matching (pattern) information indicated by the RMI field ofmulti-TTI DCI may be applied only to one specific PDSCH (e.g., the firstor last PDSCH in time) among a plurality of PDSCHs scheduled by the DCI.

3) Opt 3

A. A PDSCH among a plurality of PDSCHs scheduled by multi-TTI DCI, towhich rate-matching (pattern) information indicated by the RMI field ofthe multi-TTI DCI is to be applied, may be indicated by the same DCI orby the RRC.

(Proposal 3) ZP-CSI-RS Trigger (ZCR) Field Information

1) Opt 1

A. ZP-CSI-RS information (rate-matching information for a ZP-CSI-RS)indicated by a ZCR field of multi-TTI DCI may be applied commonly to allof a plurality of PDSCHs scheduled by the DCI. For example, the DCI mayinclude one ZCR field applied commonly to the plurality of PDSCHs. Anaperiodic ZP CSI-RS triggered by the ZCR field may be applied to allslots including the PDSCHs scheduled by the DCI.

2) Opt 2

A. ZP-CSI-RS information (rate-matching information for a ZP-CSI-RS)indicated by the ZCR field of multi-TTI DCI may be applied only to aspecific PDSCH (e.g., the first or last PDSCH in time) among a pluralityof PDSCHs scheduled by the DCI.

3) Opt 3

A. A PDSCH among a plurality of PDSCHs scheduled by multi-TTI DCI, towhich ZP-CSI-RS information (rate-matching information for a ZP-CSI-RS)indicated by the ZCR field of multi-TTI DCI is to be applied, may beindicated by the same DCI or by the RRC.

(Proposal 4) Configuration of NDI, RV, and MCS Fields

(Proposal 4-A) Configuration of NDI Field Information

1) Opt 1

A. In a situation in which the maximum number of TBs transmittable onone PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTIDCI, a 1-bit NDI field may be configured/indicated for each TB (i.e.,two 1-bit NDI fields are configured/indicated for each PDSCH). On thecontrary, when more than K PDSCHs are scheduled by the multi-TTI DCI, a1-bit NDI field is configured/indicated for each PDSCH (i.e., two TBstransmitted on one PDSCH are scheduled based on the same one 1-bit(TB-common) NDI value).

B. Regarding the value of K in the above example, K=1 in one example orK=N/2 in another example. In another example, the value of K may beconfigured by the RRC.

C. In another method, it may be configured by the RRC whether the methodof Opt 1 is to be applied or a 1-bit NDI field is configured/indicatedfor each TB all the time irrespective of the number of scheduled PDSCHs.

D. In another example, when spatial bundling is not configured for anHARQ-ACK feedback, a 1-bit NDI field may be configured/indicated foreach TB all the time irrespective of the number of scheduled PDSCHs.When spatial bundling is configured for an HARQ-ACK feedback, the methodof Opt 1 may be applied, or a 1-bit (TB-common) NDI field may beconfigured/indicated for each PDSCH all the time irrespective of thenumber of scheduled PDSCHs.

E. In another example, when spatial bundling is not configured for anHARQ-ACK feedback, a 1-bit NDI field may be configured/indicated foreach TB all the time irrespective of the number of scheduled PDSCHs.When spatial bundling is configured for an HARQ-ACK feedback, it may beconfigured by the RRC whether the method of Opt 1 is to be applied (or a1-bit (TB-common) NDI field is configured/indicated for each PDSCH allthe time irrespective of the number of scheduled PDSCHs) or a 1-bit NDIfield is configured/indicated for each TB all the time irrespective ofthe number of scheduled PDSCHs.

2) Opt 2

A. In a situation in which the maximum number of TBs transmittable onone PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTIDCI, up to two TBs are transmittable on each PDSCH (in this case, two1-bit NDI fields are configured/indicated for each PDSCH, that is, a1-bit NDI field is configured/indicated for each TB (each of two TBs)transmittable on the PDSCH). On the contrary, when more than K PDSCHsare scheduled by the multi-TTI DCI, only one TB is transmittable on eachPDSCH (in this case, one 1-bit NDI field may be configured/indicated foreach PDSCH by DCI, that is, only a 1-bit NDI field may beconfigured/indicated for one TB transmittable on the PDSCH).

B. Regarding the value of K in the above example, K=1 in one example orK=N/2 in another example. In another example, the value of K may beconfigured by the RRC.

C. The operation method of Opt 2 based on K=1 is referred to as “2-TBonly for single PDSCH”, for convenience.

(Proposal 4-B) Configuration of RV Field Information

1) Opt 1

A. In a situation in which the maximum number of TBs transmittable onone PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTIDCI, a 2-bit RV field may be configured/indicated for each TB (i.e., two2-bit RV fields may be configured/indicated for each PDSCH). On thecontrary, when more than K PDSCHs are scheduled by the multi-TTI DCI, a2-bit RV field may be configured/indicated for each PDSCH (i.e., two TBstransmitted on one PDSCH may be scheduled based on the same one 2-bit RVvalue).

B. Regarding the value of K in the above example, K=1 in one example orK=N/2 in another example. In another example, the value of K may beconfigured by the RRC.

2) Opt 2

A. In a situation in which the maximum number of TBs transmittable onone PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTIDCI, a 2-bit RV field may be configured/indicated for each TB (i.e., two2-bit RV fields may be configured/indicated for each PDSCH). On thecontrary, when more than K PDSCHs are scheduled by the multi-TTI DCI, a1-bit RV field may be configured/indicated for each PDSCH (i.e., two TBstransmitted on one PDSCH may be scheduled based on the same one 1-bit RVvalue).

B. Regarding the value of K in the above example, K=1 in one example orK=N/2 in another example. In another example, the value of K may beconfigured by the RRC.

3) Opt 3

A. In a situation in which the maximum number of TBs transmittable onone PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTIDCI, a 1-bit RV field may be configured/indicated for each TB (i.e., two1-bit RV fields may be configured/indicated for each PDSCH). On thecontrary, when more than K PDSCHs are scheduled by the multi-TTI DCI, a1-bit RV field may be configured/indicated for each PDSCH (i.e., two TBstransmitted on one PDSCH may be scheduled based on the same one 1-bit RVvalue).

B. Regarding the value of K in the above example, K=1 in one example orK=N/2 in another example. In another example, the value of K may beconfigured by the RRC.

4) Opt 4

A. In a situation in which the maximum number of TBs transmittable onone PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTIDCI, up to 2 TBs are transmittable on each PDSCH (in this case, two2-bit (or 1-bit) RV fields may be configured/indicated for each PDSCH,that is, a 2-bit (or 1-bit) RV field may be configured/indicated foreach TB (each of two TBs) transmittable on the PDSCH). On the contrary,when more than K PDSCHs are scheduled by the multi-TTI DCI, only one TBis transmittable on each PDSCH (in this case, a 1-bit (or 2-bit) RVfield may be configured/indicated for each PDSCH, that is, a 1-bit (or2-bit) RV field may be configured/indicated for one TB transmittable onthe PDSCH).

B. Regarding the value of K in the above example, K=1 in one example orK=N/2 in another example. In another example, the value of K may beconfigured by the RRC.

5) Note

A. In Opt 1/2/3/4, the number of PDSCHs may mean the number of actuallytransmitted valid PDSCHs except for an invalid PDSCH the transmission ofwhich is skipped/dropped due to overlap with a specific UL symbol (e.g.,semi-statically configured by higher-layer signaling such astdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), orthe total number of PDSCHs indicated by multi-TTI DCI irrespective ofwhether the PDSCHs are actually transmitted.

B. In another example, when a plurality of PDSCHs (or PUSCHs) arescheduled by multi-TTI DCI (e.g., a state composed of/configured with aplurality of SLIVs is indicated by the TDRA field), it may be regulatedthat the number of actually transmitted valid PDSCHs (or PUSCHs) exceptfor invalid PDSCHs (or PUSCHs) whose transmissions are dropped due tooverlap in time with a specific (e.g., semi-statically configured) UL(or DL) symbol among the plurality of PDSCHs (or PUSCHs) is always 2 orlarger (the UE may expect/assume such scheduling from the BS).Otherwise, when the number of valid PDSCHs (or PUSCHs) is less than 2,the UE may discard the multi-TTI DCI, considering that the multi-TTI DCIis an inconsistent PDCCH.

C. When an SCell dormancy indication is performed, which indicatesswitching to a dormant BWP configured to allow the UE to skip PDCCHmonitoring in a specific SCell without PDSCH scheduling by legacysingle-TTI DCI, 3 bits corresponding to a 1-bit NDI and a 2-bit RV inthe DCI is reinterpreted as a part of SCell dormancy indicationinformation.

When an SCell dormancy indication is performed without PDSCH schedulingby multi-TTI DCI, Alt 1) a 1-bit DNI and a 2-bit RV configured tocorrespond to one indicated PDSCH under the constraint that only onePDSCH (e.g., a single SLIV) is always indicated by the TDRA field of theDCI may be reinterpreted as SCell dormancy indication information, Alt2) the first or last 3 bits of a total bit set including (one or) aplurality of NDI fields and RV fields corresponding to (one or) aplurality of PDSCHs indicated by the DCI without the constraint of Alt 1may be reinterpreted as SCell dormancy indication information, or Alt 3)the first or last one bit of (one or) a plurality of NDI field setscorresponding to (one or) a plurality of PDSCHs and the first or last 2bits of (one or) a plurality of RV field sets corresponding to the (oneor) plurality of PDSCHs indicated by the DCI without the constraint ofAlt 1 may be reinterpreted as SCell dormancy indication information.

(Proposal 4-C) Configuration of MCS Field Information

1) Opt 1

A. In a situation in which the maximum number of TBs transmittable onone PDSCH is set to 2, when K or fewer PDSCHs are scheduled by multi-TTIDCI, up to two TBs are transmittable on each PDSCH (in this case, twoMCS fields may be configured/indicated for each PDSCH by the DCI, thatis, an MCS field may be configured/indicated for each TB (each of twoTBs) transmittable on the PDSCH), whereas when more than K PDSCHs arescheduled by the multi-TTI DSCI, only one TB is transmittable on eachPDSCH (in this case, one MCS field may be configured/indicated for eachPDSCH by the DCI, that is, only an MCS field may be configured/indicatedfor one TB transmittable on the PDSCH).

B. Regarding the value of K in the above example, K=1 in one example orK=N/2 in another example. In another example, the value of K may beconfigured by the RRC.

2) Note

A. When more than K PDSCHs are scheduled by multi-TTI DCI, only one TBis transmittable on each PDSCH based on the above proposals.Accordingly, the numbers of MCS fields, RV fields, and NDI fieldsconfigured/indicated by the DCI are reduced. In this case, unusedMCS/RV/NDI bits may be used to indicate other information.

B. For example, in a state in which a plurality of PDSCHs (more than KPDSCHs) scheduled by one multi-TTI DCI have been grouped into aplurality of (e.g., 2) groups, an HARQ-ACK feedback corresponding toeach individual group may be transmitted by applying/using an HARQ-ACKtiming and a PUCCH resource indicated by individual K1 and PRI fieldsfor the group. Unused MCS/RV/NDI bits may be used to configure(individual) K1 and PRI fields on a group basis.

(Proposal 5) Configuration of HARQ Process ID Information

1) Opt 1

A. When some specific of a plurality of PDSCHs scheduled by multi-TTIDCI overlap with specific UL symbol(s) (e.g., UL symbol(s) staticallyconfigured by higher-layer signaling such astdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated),transmission and reception of the specific PDSCH(s) may beskipped/dropped. In this case, consecutive HARQ process IDs startingfrom an HARQ process ID indicated by the DCI may be allocatedsequentially in time only to actually transmitted/received PDSCH(s)(instead of the scheduled PDSCHs). For example, on the assumption that asingle DL grant DCI schedules 8 PDSCHs and two PDSCHs collide with a ULsymbol and thus are dropped, 6 consecutive HARQ process IDs {HARQprocess ID #n+1 to HARQ process ID #n+6} may be sequentially allocatedto a total of 6 valid PDSCHs.

FIG. 8 illustrates exemplary HARQ-process ID allocation for multi-TTIscheduling. Referring to FIG. 8 , it is assumed that a TDRA fieldindicates row index k and an HARQ process ID field indicates n in DCI.In a TDRA table, an indexed row includes a total of three SLIV valuescorresponding to PDSCH 1, PDSCH 2, and PDSCH3 (in time order). Becausean SLIV value for PDSCH 2 overlaps with a U symbol, PDSCH 2 becomes aninvalid PDSCH. Therefore, HARQ process IDs are sequentially/continuouslyallocated only to valid PDSCH 1 and PDSCH 3 except for the invalidPDSCH.

Accordingly, regarding the NDI and RV fields corresponding to eachPDSCH, consecutive NDI/RV fields starting from the last (or first)NDI/RV field in the DCI may correspond in time only to the actuallytransmitted/received PDSCH(s).

Similarly, UL grant DCI may sequentially allocate HARQ process IDs tovalid PUSCHs, except for invalid PUSCHs that collide with asemi-statically configured DL symbol and thus are dropped.

2) Opt 2

When some specific of a plurality of PDSCHs scheduled by multi-TTI DCIoverlap with a specific (e.g., semi-statically configured) UL symbol,transmission and reception of the specific PDSCH(s) may be dropped. Inthis case, consecutive HARQ process IDs starting from an HARQ process IDindicated by the DCI may be allocated to all PDSCH(s) scheduled by theDCI in time order regardless of whether the PDSCH(s) are actuallytransmitted/received.

A. Accordingly, consecutive NDI/RV fields starting from the last (orfirst) NDI/RV field in the DCI may correspond to all PDSCH(s) scheduledby the DCI in time order, regardless of whether the PDSCH(s) is actuallytransmitted/received.

3) Note

A. When some specific of a plurality of PUSCHs scheduled with multi-TTIDCI overlap with a specific (e.g., semi-statically configured) DLsymbol, the above methods may also be applied equally by determining anHARQ process ID and a corresponding NDI/RV field for each PUSCH.

B. To prevent complexity/ambiguity in determining NDI/RV, CBGTI/CBGFI,HARQ-ACK timing, and PDSCH TCI/QCL information as well as HARQ processIDs and configuring corresponding fields, it may be regulated that thefirst of a plurality of PDSCHs/PUSCHs scheduled/indicated by multi-TTCDCI is always scheduled/indicated as a valid PDSCH/PUSCH that does notoverlap with a specific (e.g., semi-statically configured) UL/DL symbolby the DCI (the UE assumes such scheduling). Accordingly, when the firstPDSCH/PUSCH scheduled/indicated by the multi-TTI DCI overlaps with thespecific (e.g., semi-statically configured) UL/DL symbol, the UE maydiscard the DCI (considering the DCI as an inconsistent PDCCH).

(Proposal 6) Configuration of CBGTI and CBGFI Field Information

1) Opt 1

A. In a situation in which a PDSCH transmissions based on up to M CBgroups (CBGs) is configured, when K or fewer PDSCHs are scheduled bymulti-TTI DCI, an M-bit CBG transmission indicator (CBGTI) field and a1-bit CBG flush indicator (CBGFI) field may be configured/indicated foreach PDSCH, whereas when more than K PDSCHs are scheduled by themulti-TTI DCI, neither the CBGTI field nor the CBGFI field may beconfigured/indicated (i.e., all scheduled PDSCHs may be transmitted at aTB level (not based on a CBG)).

B. Regarding the value of K in the above example, K=1 in one example orK=N/2 in another example. In another example, the value of K may beconfigured by the RRC.

C. The operation method of Opt 1 based on K=1 is referred to as “CBGonly for single PDSCH”, for convenience.

2) Opt 2

A. In a situation in which a PDSCH transmissions based on up to M CBGsis configured, when K or fewer PDSCHs are scheduled by multi-TTI DCI,only one 1-bit CBGFI field may be configured/indicated, and an M-bitCBGTI field may be configured/indicated for each PDSCH, whereas whenmore than K PDSCHs are scheduled by the multi-TTI DCI, neither the CBGTIfield nor the CBGFI field may be configured/indicated (i.e., allscheduled PDSCHs may be transmitted at a TB level (not based on a CBG)).

B. A value indicated by the single 1-bit CBGFI field may be commonlyapplied to all of a plurality of scheduled PDSCHs, or only to a specificone (e.g., the first or last one in time) of the plurality of PDSCHs.

C. Regarding the value of K in the above example, K=2 in one example orK=N/2 in another example. In another example, the value of K may beconfigured by the RRC.

3) Note

A. In Opt 1/2, the number of PDSCHs may mean the number of valid PDSCHswhich are actually transmitted, except for invalid PDSCHs which overlapwith a specific (e.g., semi-statically set) UL symbol and thetransmissions of which are dropped, or may mean the total number ofPDSCHs indicated by multi-TTI DCI regardless of whether they areactually transmitted.

B. Based on the above proposals, the size or the presence or absence ofa specific field (e.g., NDI, RV, MCS, CBGTI, CBGFI, or the like) inmulti-TTI DCI may be determined differently depending on whether thenumber of PDSCHs scheduled by the DCI is equal to or less than K, orgreater than K, and as different K values are defined/set betweenspecific fields, a total of L different K values {K_1, . . . , K_L} mayexist.

i. Alternatively, the same K value may be defined/set between thespecific fields, and thus L=1.

C. Additionally, on the assumption that the maximum number of PDSCHsthat may be indicated/scheduled by the TDRA field of multi-TTI DCI isK_max, a total of L+1 different K values {K_1, . . . , K_L, K_max} mayexist.

D. Accordingly, a total DCI payload size may be calculated on theassumption that as many PDSCHs as a corresponding K value are scheduled(by multi-TTI DCI), for each of the L+1 different K values {K_1, . . . ,K_L, K_max}, and the maximum of the calculated DCI payload sizescorresponding to the L+1 K values may be determined as a final payloadsize of the multi-TTI DCI (format).

(Proposal 7) Signaling of DAI Field Information (Configuration of Type-2A/N Codebook Based on the Signaling)

1) Signaling of Counter-DAI and Total-DAI in DL DCI

A. A case in which one PDSCH is scheduled by any DCI (e.g., existingsingle-TTI DCI or multi-TTI DCI) is defined as a single PDSCH case, anda case in which a plurality of PDSCHs are scheduled by multi-TTI DCI isdefined as a multiple PDSCH case. Then, a counter/total-DAI value may beindependently determined and signaled for each of the single PDSCH caseand the multiple PDSCH case (i.e., DCI/PDSCH sequence/sum scheduled foreach case may be independently determined/signaled).

B. In other words, DCI corresponding to the single PDSCH case maydetermine and signal a DAI value only for the single PDSCH case, and DCIcorresponding to the multiple PDSCH case may determine and signal a DAIvalue only for the multiple PDSCH case. In other words, a C-DAI/T-DAIrelated to the single PDSCH case may be counted within DCI(s) related tothe single PDSCH case, and a C-DAI/T-DAI related to the multiple PDSCHcase may be counted within DCI(s) related to the multiple PDSCH case.

C. The number of A/N bits corresponding to one DAI in the multiple PDSCHcase may be determined based on the maximum number of TBs (including acase where spatial bundling is not configured) or the maximum number ofPDSCHs (including a case in which spatial bundling is configured), whichmay be scheduled by any (serving cell) multi-TTI DCI.

D. The above-described method may be applied to a situation in which aCBG-based PDSCH transmission is not configured.

2) Signaling of UL (Total) DAI in UL DCI

A. A UL DAI value may be signaled for each of the single PDSCH case andthe multiple PDSCH cases (i.e., two UL DAI values may be signaled by oneDCI, indicating total-DAI information for the single PDSCH case andtotal-DAI information for the multiple PDSCH case, respectively).

B. The above-described method may be applied to a situation in which aCBG-based PDSCH transmission is not configured.

3) DAI Signaling in Situation in which CBG-Based PDSCH Transmission isConfigured

A. A case in which a CBG-based PDSCH transmission is scheduled byspecific DCI (e.g., DCI including a CBGTI field/signaling) is defined asa CBG PDSCH case, a case in which one TB-based PDSCH transmission (i.e.,one PDSCH transmission based on a TB) is scheduled by any DCI is definedas a single PDSCH case, and a case in which a plurality of (TB-based)PDSCH transmissions (i.e., a plurality of TB-based PDSCH transmissions)are scheduled by multi-TTI DCI is defined as a multiple PDSCH case.Then, a counter/total-DAI value may be determined/signaled in thefollowing manner.

B. Opt 1: A counter/total-DAI value may be determined and signaledindependently for each of the three cases, that is, the single PDSCHcase, the multiple PDSCH case, and the CBG PDSCH case. Regarding a ULDAI, a UL DAI value may be signaled for each of the above-describedthree cases (the single PDSCH case, the multiple PDSCH case, and the CBGPDSCH case) by DCI.

C. Opt 2: If the multiple PDSCH case and the CBG PDSCH case arecollectively defined as a multi-A/N PDSCH case, a counter/total-DAIvalue may be determined and signaled independently for each of the twocases, that is, the single PDSCH case and the multi-A/N PDSCH case.

D. In the case of Opt 2, DCI corresponding to the single PDSCH maysignal a determined DAI value only for the single PDSCH case, and DCIcorresponding to the multi-A/N PDSCH case (i.e., the multiple PDSCH caseor the CBG PDSCH case) may signal a determined DAI value only for themulti-A/N PDSCH case (i.e., the multiple PDSCH case and the CBG PDSCHcase).

E. In the multi-A/N PDSCH case, when the maximum number of TBs(including the case where spatial bundling is not configured) or themaximum number of PDSCHs (including the case where spatial bundling isconfigured) schedulable by any multi-TTI DCI (in a serving cell) isdefined as A, and the maximum number of CBGs configured for any PDSCHtransmission (in a serving cell) is defined as B, the number of A/N bitscorresponding to one DAI may be determined based on the larger between Aand B.

(Proposal 8) HARQ Timing Field Information (Configuration of Type-1/2A/N Codebook Based on HARQ Timing Field Information)

1) A/N Timing Determination and A/N Payload Configuration for Type-2 A/NCodebook

A. An A/N timing (slot) may be determined by applying a K1 value(indicated by multi-TTI DCI) based on the last (or first) PDSCHtransmission slot (in time) among a plurality of PDSCHs scheduled by theDCI, and A/N feedbacks for all of the plurality of PDSCHs scheduled bythe DCI may be transmitted at one time at the (same one) A/N timing.

B. Accordingly, a counter/total-DAI value may be determined/signaledonly between multi-TTI DCIs indicating the A/N timing corresponding tothe last (or first) PDSCH transmission slot as the same slot, and A/Nfeedbacks for all of a plurality of PDSCHs scheduled by the multi-TTIDCIs (indicating the A/N timing corresponding to the last (or first)PDSCH transmission slot as the same slot) may be multiplexed andtransmitted at the same one A/N timing.

C. In the above example, the last (or first) PDSCH may refer to the last(or first) one of actually transmitted valid PDSCHs except for invalidPDSCHs which overlap with a specific (e.g., semi-statically set) ULsymbol and thus the transmissions of which are dropped, or the last (orfirst) one of PDSCHs indicated by multi-TTI DCI regardless of whetherthey are actually transmitted.

2) A/N Timing Determination and A/N Payload Configuration for Type-1 A/NCodebook

A. An A/N timing (slot) may be determined by applying a K1 value(indicated by multi-TTI DCI) based on the last (or first) PDSCHtransmission slot (in time) among a plurality of PDSCHs scheduled by theDCI, and A/N feedbacks for all of the plurality of PDSCHs scheduled bythe DCI may be transmitted at one time at the (same one) A/N timing.

B. Accordingly, A/N feedbacks (for all of plurality of PDSCHs scheduledby multi-TTI DCIs) may be multiplexed and transmitted at the same oneA/N timing only between the multi-TTI DCIs indicating an A/N timingcorresponding to the last (or first) PDSCH transmission slot as the sameslot (single-TTI DCIs indicating an A/N timing corresponding to the last(or first) PDSCH transmission slot as the same slot).

C. In the above example, the last (or first) PDSCH may refer to the last(or first) one of actually transmitted valid PDSCHs except for invalidPDSCHs which overlap with a specific (e.g., semi-statically set) ULsymbol and thus whose transmissions are dropped, or the last (or first)one of PDSCHs indicated by multi-TTI DCI regardless of whether they areactually transmitted.

D. In a state in which a set of a plurality of (e.g., N) candidate K1values (e.g., a set of PDSCH-to-HARQ feedback timing indicator valueswhich may be indicated by DCI) are set, in the case of the legacy Type-1codebook, a combination of all PDSCH occasions (SLIVs) transmittable ina DL slot earlier than an A/N transmission slot by K1 DL slots arecalculated for each K1 value (configured for a corresponding servingcell on a serving cell basis), and A/N sub-payload corresponding to thecorresponding DL slot may be configured (including determination of anA/N bit position/sequence corresponding to each SLIV). (This is definedas “SLIV pruning”). A process of determining combinations oftransmittable PDSCH occasions (SLIVs) in SLIV pruning will be describedin more detail. One or more non-overlapping PDSCHs may be scheduled fora UE in each DL slot (e.g., index #N-candidate K1 value). The number ofnon-overlapping PDSCHs (the maximum number of non-overlapping PDSCHsschedulable in the corresponding slot) may be determined based on acombination of configured SLIV values (e.g., a combination of SLIVsconfigured through pdsch-TimeDomainAllocationList and indicated by theTDRA field of DCI). Based on the SLIV values set for the UE, a processof pruning potential overlapping PDSCHs (i.e., incompatible/mutuallyexclusive PDSCHs due to overlap are counted as a maximum of one PDSCHtransmission), and determining (schedulable/compatible potential)non-overlapping PDSCHs is referred to as SLIV pruning. In the case ofthe existing Type-1 codebook, A/N sub-payloads configured by the SLIVpruning may be concatenated for N K1 values to configure the entire A/Ncodebook (e.g., refer to 3GPP TS 38.213 V16.2.0 Section 9.1.2).

For convenience of description, a set of (N) DL slots corresponding toeach K1 value may be referred to as a bundling window corresponding tothe A/N transmission slot. For example, on the assumption that(candidate) K1 value set={2, 3} that may be indicated by DCI asillustrated in FIG. 9 , the bundling window is a period from Slot #N-3to Slot #-2.

E. It may occur that among a plurality of PDSCH transmission slotsscheduled (or schedulable) by multi-TTI DCI which indicates (or mayindicate) a specific slot as an A/N timing (corresponding the last (orfirst) PDSCH transmission slot), a specific slot does not belong to thebundling window corresponding to the A/N transmission slot.

For example, an A/N codebook determined according to the existing SLIVpruning method for the legacy single PDSCH scheduling may not cover atleast part of multiple scheduled PDSCHs. In a more specific example,referring to FIG. 9 , it is assumed that (i) two rows of a TDRA tableare indictable by multi-PDSCH DCI, and (ii) each row includes two SLIVs(i.e., each row is related to scheduling of two PDSCHs), (iii) a K1 slotoffset value being a PDSCH-to-HARQ-ACK timing is set to 2 (e.g., K1value set={2, 3}). In a situation in which as PDSCH1 in slot #N-4 andPDSCH2 in slot #N-3 are scheduled by multi-PDSCH scheduling DCI (e.g.,TDRA row 0), and K1=3 is indicated, an HARQ-ACK is transmitted in slot#N, the UE should report not only an A/N for Slot #N-3 (i.e., PDSCH2corresponding to K1=3) belonging to the bundling Window, but also PDSCH1(e.g., a PDSCH related to an extended K1 value) in slot #N-4 that doesnot belong to the bundling window. However, when the existing method(i.e., the SLIV pruning method for single PDSCH scheduling) is appliedas it is, the UE drops A/N sub-payload for PDSCH1 in slot #N-4 becauseK1=4 is not included in the determined K1 value set. To solve theproblem, an A/N codebook may be configured in the following manneraccording to an example of the present disclosure.

F. Opt 1: Basically, even for each of DL slots that do not belong to abundling window (corresponding to a corresponding A/N transmission slotamong DL slots schedulable by multi-TTI DCI that may indicate (aspecific slot as) an A/N timing (corresponding to the last (or first)PDSCH transmission slot) (for every SLIV set schedulable in acorresponding DL slot by any multi-TTI DCI), the UE may configure A/Nsub-payload by SLIV pruning. For example, the UE configures 1-bit A/Nsub-payload even for slot #N-4 that does not belong to the bundlingwindow by performing the SLIV pruning process in FIG. 9 . Regardingmulti-TTI scheduling, the UE may perform SLIV pruning even for a DL slotthat does not belong to the bundling window as a result of considering aK0 value in each row=={{K0, mapping type, SLIV) for PDSCH1, {K0, mappingtype, SLIV) for PDSCH2 . . . } in a TDRA table for the corresponding DLslot. In FIG. 9 , slot #N-4 in which PDSCH1 is transmitted may bedetermined by K0 for PDSCH1 in the TDRA Table. As described above, in astate in which A/N sub-payload has been configured for each of DL slotsthat do not belong to the bundling window by performing the SLIV pruningprocess, the UE may operate as follows:

i. Opt a) An entire A/N codebook may be configured by mapping an A/Nsub-payload set corresponding to the DL slots belonging to the bundlingwindow, and then mapping the A/N sub-payload set corresponding to the DLslots that do not belong to the bundling window.

ii. Opt b) Alternatively, an entire A/N codebook may be configured bysequentially concatenating the A/N sub-payload of all DL slots belongingto the bundling window and all DL slots not belonging to the bundlingwindow in time order of the DL slots.

iii. In this case, for each of the DL slots belonging to the bundlingwindow, A/N sub-payload may be configured by performing SLIV pruning onall SLIV sets schedulable for the DL slot by any single-TTI DCI and/ormulti-TTI DCI.

G. Opt 1A: In another method equivalent to Opt 1 (e.g., when slot #N isindicated as an A/N transmission timing), the following operation may beconsidered.

i. Step 1) As each row (including one or more SLIVs) in a TDRA tableconfigured by multi-TTI DCI indicates each K1 configured for the UE (orconfigured in the multi-TTI DCI) (e.g., the last SLIV in the row ismapped to slot #(N−K1)), all K1_m values may be calculated on theassumption that each SLIV in the row is mapped to slot #(N−K1_m), andthis process may be performed for all rows and all K1 values. Then, theunion (defined as “K1_m Union” for convenience) of all K1_m values maybe calculated.

1. Additionally, for specific single-TTI DCI (e.g., a DCI format whichis not fallback DCI format 1_0 and does not configure multi-TTIscheduling), the UE may also include all K1 values configured for the UE(or in the DCI) in the K1_m Union (as K1_m values belonging to the K1_mUnion).

ii. Step 2) A/N sub-payload may be configured by performing the SLIVpruning process for all SLIV sets mappable to slot #(N−K1_m)corresponding to each K1_m value belonging to the K1_m Union (from amongthe SLIVs in the rows in the TDRA table of the multi-TTI DCI and therows in the TDRA table of the single-TTI DCI), and an entire A/Ncodebook may be configured by applying the method of Opt a or Opt b toeach of the K1_m values or A/N sub-payload corresponding to each slot#(N−K1_m).

1. For example, for each SLIV group (including one or more (overlapped)SLIVs) determined through SLIV pruning for each of all K1_m values inthe K1_m Union configured for each cell (this is defined as “HARQ-ACKPDSCH occasion (HPO)”), A/N sub-payload may be configured by allocating2 bits (when the cell is configured with a PDSCH transmission of up to 2TBs, and not with HARQ-ACK spatial bundling), 1 bit (when the cell isconfigured with a PDSCH transmission of up to 1 TB or with HARQ-ACKspatial bundling), or M bits (when the cell is configured with a PDSCH(or TB) transmission based on up to M CBGs).

2. In another example, when a “2-TB only for single PDSCH” operation isapplied to the cell configured with a PDSCH transmission of up to 2 TBs(and not with spatial bundling) (and when there is a row including onlyone SLIV among the rows of the TDRA table configured in multi-TTI DCI(format) (this is called a “single-SLIV row”)), or when there isspecific single-TTI DCI configuring a PDSCH transmission of up to twoTBs (e.g. when there is DCI (format) which is not fallback DCI format1_0 and does not configure multi-TTI scheduling), 2 bits may beallocated to HPO(s) corresponding to a value matching K1 in the K1_mUnion configured for the corresponding cell or slot #(N−K1)corresponding to this value (slot #(N−K1) belonging to the bundlingwindow) (or HPO(s) corresponding to the single-SLIV row or rows in theTDRA table configured for a single TTI), whereas 1 bit may be allocatedHPO(s) corresponding to a K1_m value that does not match K1 or slot#(N−K1_m) (not belonging to the bundling window) corresponding to thisvalue (or the remaining HPO(s) corresponding to slot #(N−K1), includingthe HPO(s)).

3. In another example, when a “CBG only for single PDSCH” operation isapplied to the cell configured with an up to M CBGs-based PDSCHtransmission (and when there is a row including only one SLIV among therows of the TDRA table configured in multi-TTI DCI (format) (this iscalled a “single-SLIV row”)), or when there is specific single-TTI DCIconfiguring an up to M CBGs-based PDSCH transmission (e.g. when there isDCI (format) which is not fallback DCI format 1_0 and does not configuremulti-TTI scheduling), M bits may be allocated to HPO(s) correspondingto a value matching K1 in the K1_m Union configured for thecorresponding cell or slot #(N−K1) corresponding to this value (slot#(N−K1) belonging to the bundling window) (or HPO(s) corresponding tothe single-SLIV row or rows in the TDRA table configured for a singleTTI), whereas 1 bit may be allocated to HPO(s) corresponding to a K1_mvalue that does not match K1 or slot #(N−K1_m) (not belonging to thebundling window) corresponding to this value (or the remaining HPO(s)corresponding to slot #(N−K1), including the HPO(s)).

iii. When some of a plurality of SLIVs configured in one row of a TDRAtable in multi-TTI DCI overlaps with a specific UL symbol (e.g., a ULsymbol configured semi-statically by higher-layer signaling bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) indetermining a K1_m Union and performing the SLIV pruning process, theK1_m Union may be determined, and the SLIV pruning may be performed(based on the determined K1_m Union) while excluding the correspondingSLIV. For example, the UE may consider a PDSCH corresponding to the SLIVoverlapping with the UL symbol as an invalid PDSCH, and may perform theSLIV pruning process only on valid PDSCHs.

H. Opt 1B: To reduce UE complexity involved in the SLIV pruning processin Opt 1 or 1A, the following operation may be considered.

i. Step 1) A K1_m Union is calculated in the same process as Step 1 ofOpt 1A, an SLIV set (defined as an “m-SLIV Union”) is calculated on theassumption that all (of one or more) individual SLIVs configured in eachrow of a TDRA table configured in multi-TTI DCI are mapped to one(virtual) slot, and an SLIV set (defined as an “s-SLIV union”) iscalculated on the assumption that all SLIVs configured in each row of aTDRA table configured in single-TTI DCI are mapped to one (virtual)slot.

1. Alternatively, an SLIV set based on the assumption that all (plural)individual SLIVs set in each of all rows configured with SLIVs acrossmultiple slots in a TDRA table configured in multi-TTI DCI are mapped tothe same single (virtual) slot is determined as an “m-SLIV Union”, andan SLIV set based on the assumption that all (of one or more) individualSLIVs set in each of all rows configured with SLIVs belonging to asingle slot in a TDRA table configured in multi-TTI DCI and SLIVsconfigured in each of all rows in a TDRA table configured in single-TTIDCI are mapped to the same one (virtual) slot is determined as an“s-SLIV Union”.

2. Alternatively, an SLIV set based on the assumption that all (plural)individual SLIVs set in each of all rows configured with a plurality ofSLIVs in a TDRA table configured in multi-TTI DCI are mapped to the samesingle (virtual) slot is determined as an “m-SLIV Union”, and an SLIVset based on the assumption that all individual SLIVs set in all rowseach configured with a single SLIB in a TDRA table configured inmulti-TTI DCI, and SLIVs set in each of all rows in a TDRA tableconfigured in single-TTI DCI are mapped to the same one (virtual) slotis determined as an “s-SLIV Union”.

ii. Step 2—Alt 1) A/N sub-payload may be configured by performing theSLIV pruning process for a union of all SLIVs belonging to the m-SLIVunion and the s-SLIV union, for a value matching K1 in the K1_m Union ora corresponding slot #(N−K1) (belonging to a bundling window), and A/Nsub-payload may be configured by performing the SLIV pruning processonly for SLIVs belonging to the m-SLIV union, for a K1_m value notmatching K1 or the corresponding slot #(N−K1_m) (not belonging to thebundling window). Then, an entire A/N codebook may be configured byapplying the method of Opt a or Opt b to A/N sub-payload correspondingto each of the K1_m values or each slot #(N−K1_m).

1. For example, for each SLIV group (including one or more (overlapped)SLIVs) determined through SLIV pruning for each of all K1_m values inthe K1_m union configured for each cell (this is defined as “HARQ-ACKPDSCH occasion (HPO)”), A/N sub-payload may be configured by allocating2 bits (when the cell is configured with a PDSCH transmission of up to 2TBs, and not with HARQ-ACK spatial bundling), 1 bit (when the cell isconfigured with a PDSCH transmission of up to 1 TB or with HARQ-ACKspatial bundling), or M bits (when the cell is configured with an up toM CBGs-based PDSCH (or TB) transmission).

2. In another example, when a “2-TB only for single PDSCH” operation isapplied to the cell configured with a PDSCH transmission of up to 2 TBs(and not with spatial bundling) (and when there is a row including onlyone SLIV among the rows of the TDRA table configured in multi-TTI DCI(format) (this is called a “single-SLIV row”)), or when there isspecific single-TTI DCI configuring a PDSCH transmission of up to 2 TBs(e.g. when there is DCI (format) which is not fallback DCI format 1_0and does not configure multi-TTI scheduling), 2 bits may be allocated toHPO(s) corresponding to HPO(s) corresponding to a value matching K1 inthe K1_m Union configured for the corresponding cell or slot #(N−K1)corresponding to this value (slot #(N−K1) belonging to the bundlingwindow) (or HPO(s) corresponding to the single-SLIV row or rows in theTDRA table configured for a single TTI), whereas 1 bit may be allocatedHPO(s) corresponding to a K1_m value that does not match K1 or slot#(N−K1_m) (not belonging to the bundling window) corresponding to thisvalue (or the remaining HPO(s) corresponding to slot #(N−K1), includingthe HPO(s)).

3. In another example, when a “CBG only for single PDSCH” operation isapplied to the cell configured with an up to M CBGs-based PDSCHtransmission (and when there is a row including only one SLIV among therows of the TDRA table configured in multi-TTI DCI (format) (this iscalled a “single-SLIV row”)), or when there is specific single-TTI DCIconfiguring an up to M CBGs-based PDSCH transmission (e.g. when there isDCI (format) which is not fallback DCI format 1_0 and does not configuremulti-TTI scheduling), M bits may be allocated to HPO(s) correspondingto a value matching K1 in the K1_m Union configured for thecorresponding cell or slot #(N−K1) corresponding to this value (slot#(N−K1) belonging to the bundling window) (or HPO(s) corresponding tothe single-SLIV row or rows in the TDRA table configured for a singleTTI), whereas 1 bit may be allocated to HPO(s) corresponding to a K1_mvalue that does not match K1 or slot #(N−K1_m) (not belonging to thebundling window) corresponding to this value (or the remaining HPO(s)corresponding to slot #(N−K1), including the HPO(s)).

iii. Step 2—Alt 2) A/N sub-payload may be configured by performing theSLIV pruning process for a union of all SLIVs belonging to the m-SLIVunion and the s-SLIV union, for each of all K1_m values in a K1_m Union,and an entire A/N codebook may be configured by applying the method ofOpt a or Opt b to A/N sub-payload corresponding to each K1_m value oreach slot #(N−K1_m).

1. For example, for each SLIV group (including one or more (overlapped)SLIVs) determined through SLIV pruning for each of all K1_m values in aK1_m Union configured for each cell (this is defined as “HARQ-ACK PDSCHoccasion (HPO)”), A/N sub-payload may be configured by allocating 2 bits(when the cell is configured with a PDSCH transmission of up to 2 TBs,and not with HARQ-ACK spatial bundling), 1 bit (when the cell isconfigured with a PDSCH transmission of up to 1 TB or with HARQ-ACKspatial bundling), or M bits (when the cell is configured with an up toM CBGs-based PDSCH (or TB) transmission).

2. In another example, when a “2-TB only for single PDSCH” operation isapplied to the cell configured with a PDSCH transmission of up to 2 TBs(and not with spatial bundling) (and when there is a row including onlyone SLIV among the rows of a TDRA table configured in multi-TTI DCI(format) (this is called a “single-SLIV row”)), or when there isspecific single-TTI DCI configuring a PDSCH transmission of up to 2 TBs(e.g. when there is DCI (format) which is not fallback DCI format 1_0and does not configure multi-TTI scheduling), 2 bits may be allocated toHPO(s) corresponding to a value matching K1 in a K1_m Union configuredfor the corresponding cell or slot #(N−K1) corresponding to this value(slot #(N−K1) belonging to the bundling window) (or HPO(s) correspondingto the single-SLIV row or rows in the TDRA table configured for a singleTTI), whereas 1 bit may be allocated to HPO(s) corresponding to a K1_mvalue that does not match K1 or slot #(N−K1_m) (not belonging to thebundling window) corresponding to this value (or the remaining HPO(s)corresponding to slot #(N−K1), including the HPO(s)).

3. In another example, when a “CBG only for single PDSCH” operation isapplied to a cell configured with an up to M CBGs-based PDSCHtransmission (and when there is a row including only one SLIV among therows of a TDRA table configured in multi-TTI DCI (format) (this iscalled a “single-SLIV row”), or when there is specific single-TTI DCIconfiguring an up to M CBGs-based PDSCH transmission (e.g. when there isDCI (format) which is not fallback DCI format 1_0 and does not configuremulti-TTI scheduling), M bits may be allocated to HPO(s) correspondingto a value matching K1 in a K1_m Union configured for the correspondingcell or slot #(N−K1) corresponding to this value (slot #(N−K1) belongingto the bundling window) (or HPO(s) corresponding to the single-SLIV rowor rows in a TDRA table configured for a single TTI), whereas 1 bit maybe allocated to HPO(s) corresponding to a K1_m value that does not matchK1 or slot #(N−K1_m) (not belonging to the bundling window)corresponding to this value (or the remaining HPO(s) corresponding toslot #(N−K1), including the HPO(s)).

iv. When some of a plurality of SLIVs configured in one row of a TDRAtable in multi-TTI DCI overlaps with a specific UL symbol (e.g., a ULsymbol configured semi-statically by higher-layer signaling such astdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) indetermining a K1_m Union and an m SLIV Union and performing the SLIVpruning process, the K1_m Union and the m-SLIV Union may be determined,and the SLIV pruning may be performed (based on the determined K1_mUnion and m-SLIV Union) while excluding the corresponding SLIV.

I. Opt 2: Basically, in a state in which A/N sub-payload has beenconfigured by performing the SLIV pruning process only for each of theDL slots belonging to the bundling window as described before, thefollowing operations may be performed.

i. Opt a) When the maximum number of TBs (including a case in whichspatial bundling is not configured) or the maximum number of PDSCHs(including a case in which spatial bundling is configured) schedulableby any multi-TTI DCI is set to M, a total A/N codebook may be configuredby adding M bits (or M-X bits) to A/N sub-payload corresponding to eachK1 value, and mapping A/Ns for a plurality of PDSCHs scheduled bymulti-TTI DCI indicating the K1 value (as an A/N timing corresponding tothe last (or first) PDSCH transmission slot) to corresponding M bits (ormapping A/Ns for the remaining PDSCHs except for the last (or first)PDSCH or PDSCH(s) transmitted in the same slot as the correspondingPDSCH to the corresponding M-X bits).

1. In the above example, “adding M bits (or M-X bits) to A/N sub-payloadcorresponding to each K1 value” may mean that Alt 1) an HPO setcorresponding to the K1 value is configured (with a total of N+M orN+M−1 HPOs) by adding M or M−1 HPO(s) to N HPO(s) determined byperforming the SLIV pruning process for the K1 value, or Alt 2) an HPOset corresponding to the K1 value is configured (with a total of N×(1+M)or N×(1+M−1)=N×M HPOs) by adding M or M−1 HPO(s) to each of N HPO(s)determined by performing the SLIV pruning process for the K1 value.

{circle around (a)} Accordingly, A/N sub-payload corresponding to the K1value may be configured for each HPO by allocating 2 bits (when thecorresponding cell is configured with a PDSCH transmission of up to 2TBs and not with HARQ-ACK spatial bundling), 1 bit (when thecorresponding cell is configured with a PDSCH transmission of up to 1 TBand HARQ-ACK spatial bundling), or M bits (when the corresponding cellis configured with an up to M CBGs-based PDSCH transmission).

2. In this case, the SLIV pruning process may be performed only for thelast SLIV (or one or more SLIVs belonging to the same slot as the lastSLIV) among SLIVs set in each row of a TDRA table configured inmulti-TTI DCI.

3. In the above example, the K1 value may be limited only to a K1 valueset in the multi-TTI DCI (format), and for a K1 value not set in themulti-TTI DCI, (A/N sub-payload is configured for the K1 value based onSLIV pruning for the TDRA table as is done conventionally, and) theprocess of adding M bits (or M-X bits) as described above may beskipped.

4. In this case, on the assumption that a specific K1 value is indicatedas an A/N timing (corresponding to the last PDSCH transmission slot),when all SLIVs set in each of all rows in a TDRA table configured inmulti-TTI DCI (or all SLIVs except for the SLIVs (or the last of theSLIVs) of the last PDSCH transmission slot) overlap with a specific(e.g., semi-statically configured) UL symbol, the process of adding Mbits (or M-X bits) may also be skipped for the K1 value.

{circle around (a)} More specifically, in the case where SLIV pruning isperformed on the last SLIV in each row of the TDRA table of themulti-TTI DCI (or one or more SLIVs belonging to the same slot as thelast SLIV), for each K1 value in the example, when at least one SLIV ineach row does not overlap with a specific (e.g., semi-staticallyconfigured) UL symbol, the SLIV pruning may be performed by includingthe row (the last SLIV(s) of the row) (in this case, characteristically,the row is included for SLIV pruning, even when the last SLIV(s) of therow overlaps with the specific (e.g., semi-statically configured) ULsymbol). Otherwise, when all SLIVs in each row overlap with the specific(e.g., semi-statically configured) UL symbol, the SLIV pruning may beperformed while excluding the corresponding row (the last SLIV(s) of therow).

{circle around (b)} Accordingly, when all SLIVs (all of the remainingSLIVs except for the last SLIV(s)) in the row (to which one or moreSLIVs in the same slot as the last SLIV belong) corresponding to an HPOdetermined by performing the SLIV pruning process overlap with aspecific (e.g., semi-statically configured) UL symbol, the process ofadding M or M−1 HPOs as described above may be skipped. Otherwise, whenat least one SLIV (e.g. at least one remaining SLIV except for the lastSLIV(s)) in the row does not overlap with the specific (e.g.,semi-statically configured) UL symbol, the afore-described process ofadding M or M−1 HPOs may be performed.

5. In the above example, when a transmission of up to 2 TBs isconfigured for each PDSCH, and HARQ-ACK spatial bundling is notconfigured, X=2, whereas when a transmission of up to 1 TB is configuredfor each PDSCH or HARQ-ACK spatial bundling is configured, X=1.

ii. Opt b) In a state in which for each K1 value, the (maximum) numberof PDSCH occasions (SLIVs) which do/may not belong to the bundlingwindow (or which do/may not belong to the last (or first) PDSCHtransmission slot) (including a case in which spatial bundling isconfigured) among a plurality of PDSCHs schedulable by multi-TTI DCIindicating the K1 value or the (maximum) number (e.g., L) of TBscorresponding to the (maximum) number of PDSCH occasions (SLIVs)(including a case in which spatial bundling is not configured) iscalculated, and L bits are added to A/N sub-payload corresponding to theK1 value, a total A/N codebook may be configured by mapping A/Ns forPDSCHs not belonging to the bundling window (or to the last (or first)PDSCH transmission slot) among PDSCHs scheduled by multi-TTI DCIindicating the K1 value (as an A/N timing corresponding to the last (orfirst) PDSCH transmission slot) to the L bits.

1. In the above example, “adding L bits to A/N sub-payload correspondingto the K1 value” may mean that Alt 1) an HPO set corresponding to the K1value is configured (with a total of N+L HPOs) by adding L HPO(s) to NHPO(s) determined by performing the SLIV pruning process for the K1value, or Alt 2) an HPO set corresponding to the K1 value is configured(with a total of N×(1+L) HPOs) by adding L HPO(s) to each of N HPO(s)determined by performing the SLIV pruning process for the K1 value.

{circle around (a)} Accordingly, A/N sub-payload corresponding to the K1value may be configured for each HPO by allocating 2 bits (when thecorresponding cell is configured with a PDSCH transmission of up to 2TBs and not with HARQ-ACK spatial bundling), 1 bit (when thecorresponding cell is configured with a PDSCH transmission of up to 1 TBand HARQ-ACK spatial bundling), or M bits (when the corresponding cellis configured with an up to M CBGs-based PDSCH (or TB) transmission).

2. In this case, the SLIV pruning process may be performed only for thelast SLIV (or one or more SLIVs belonging to the same slot as the lastSLIV) among SLIVs set in each row of a TDRA table configured inmulti-TTI DCI.

3. In the above example, the K1 value may be limited only to a K1 valueset in the multi-TTI DCI (format), and for a K1 value not set in themulti-TTI DCI, (A/N payload corresponding to the K1 value is configuredbased on SLIV pruning for the TDRA table as is done conventionally, and)the above-described process of adding L bits may be skipped.

4. In this case, on the assumption that a specific K1 value is indicatedas an A/N timing (corresponding to the last PDSCH transmission slot),when all SLIVs set in each of all rows in the TDRA table configured inthe multi-TTI DCI (or all SLIVs except for the SLIVs (or the last of theSLIVs) of the last PDSCH transmission slot) overlap with a specific(e.g., semi-statically configured) UL symbol, the process of adding Lbits may also be skipped for the K1 value.

{circle around (a)} More specifically, in the case where SLIV pruning isperformed on the last SLIV in each row of the TDRA table of themulti-TTI DCI (or one or more SLIVs belonging to the same slot as thelast SLIV), for each K1 value in the example, when at least one SLIV ineach row does not overlap with a specific (e.g., semi-staticallyconfigured) UL symbol, the SLIV pruning may be performed by includingthe row (the last SLIV(s) of the row) (in this case, characteristically,the row is included for SLIV pruning, even when the last SLIV(s) of therow overlaps with the specific (e.g., semi-statically configured) ULsymbol). Otherwise, when all SLIVs in each row overlap with the specific(e.g., semi-statically configured) UL symbol, the SLIV pruning may beperformed while excluding the corresponding row (the last SLIV(s) of therow).

{circle around (b)} Accordingly, when all SLIVs (all of the remainingSLIVs except for the last SLIV(s)) in the row (to which one or moreSLIVs in the same slot as the last SLIV belong) corresponding to an HPOdetermined by performing the SLIV pruning process overlap with aspecific (e.g., semi-statically configured) UL symbol, the process ofadding L HPOs as described above may be skipped. Otherwise, when atleast one SLIV (e.g. at least one remaining SLIV except for the lastSLIV(s)) in the row does not overlap with the specific (e.g.,semi-statically configured) UL symbol, the afore-described process ofadding L HPOs may be performed.

iii. Opt c) For each K1 value, A/N sub-payload may be configured byperforming SLIV pruning on a set of all SLIVs mappable to each slot (orirrespective of mappable to the slot) included in a set of a pluralityof slots (for convenience, referred to as a “multi-TTI window”)schedulable by multi-TTI DCI indicating the K1 value (among SLIVsconfigured in the rows of the TDRA table of the multi-TTI DCI and therows of the TDRA table of single-TTI DCI), and the A/N sub-payloadconfiguration per K1 based on SLIV pruning for the multi-TTI window(each slot belonging to the multi-TTI window) may be performedsequentially for all K1 values.

In the above example, the K1 value (for which SLIV pruning is performedin the multi-TTI window) may be limited only to a K1 value set in themulti-TTI DCI (format), and for a K1 value not set in the multi-TTI DCI,A/N payload corresponding to the K1 value may be configured based onSLIV pruning for a TDRA table (for rows each configured with a singleSLIV) configured in single-TTI DCI as is done conventionally.

2. When some of a plurality of SLIVs configured in one row of the TDRAtable of the multi-TTI DCI overlaps with a specific (e.g.,semi-statically configured) UL symbol during SLIV pruning for themulti-TTI window on a K1 basis, a multi-TTI window (including slotsincluding at least one (valid) SLIV) may be determined while excludingthe SLIVs (as invalid), and SLIV pruning may be performed for themulti-TTI window.

J. In the case of A/N sub-payload configured by performing the SLIVpruning process for a specific K1 value (a DL slot corresponding to theK1 value) in all methods (e.g. Opt 1/1A/1B/2), a UE which does not havea capability of receiving a plurality of TDMed PDSCHs in one slot periodor for which the capability is not supported may configure A/Nsub-payload only with A/N bits corresponding to one PDSCH occasion. (Forexample, 2 A/N bits may be configured when a PDSCH transmission of up to2 TBs is configured, and HARQ-ACK spatial bundling is not configured,whereas 1 A/N bit may be configured when a PDSCH transmission of up to 1TB and HARQ-ACK spatial bundling are configured).

K. Additionally, the operation of performing the SLIV pruning processfor a specific K1 value and configuring A/N sub-payload (and adding M orM-X bits, or L bits to the A/N sub-payload) in all the above-describedmethods (e.g. Opt 1/1A/1B/2) may amount to an operation of performingthe SLIV pruning process and configuring A/N sub-payload (and adding Mor M-X bits, or L bits to the A/N sub-payload) on a DL slot basis, for aplurality of DL slots included in/belonging to a UL slot period earlierthan an HARQ-ACK transmission UL slot by K1 slots in a situation inwhich an SCS configured for UL (HARQ-ACK) is smaller than an SCSconfigured for DL (PDSCH).

(Proposal 9) Operation of Receiving Plural PDSCHs Scheduled By Multi-TTIDCI

1) TCI Information and QCL Assumption Applied for PDSCH Reception By UE

A. Conventionally,

i. When a time offset between DCI and a PDSCH (scheduled by the DCI) isequal to or greater than a specific threshold (e.g. timeDurationForQCL),the PDSCH may be received by applying a TCI state indicated by the DCIand an associated QCL assumption.

ii. Otherwise, when the DCI-to-PDSCH time offset is less than thespecific threshold, the PDSCH may be received by applying a TCI stateconfigured for (reception of) a specific CORESET (e.g., a CORESET havinga lowest ID) and an associated QCL assumption.

B. Regarding a plurality of PDSCHs scheduled by multi-TTI DCI, thefollowing operations may be performed:

i. Opt 1: A PDSCH (i.e., PDSCH-D) for which a DCI-to-PDSCH time offsetis equal to or greater than a specific threshold may be received byapplying a TCI state indicated by the DCI and an associated QCLassumption, whereas a PDSCH (i.e., PDSCH-C) for which a DCI-to-PDSCHtime offset is less than the specific threshold may be received byapplying a TCI state configured for (reception of) a specific CORESET(e.g., a CORESET having a lowest ID) at a specific time (e.g., in thelatest CORESET configuration slot including and/or before the firstPDSCH transmission slot among a plurality of PDSCHs) and an associatedQCL assumption commonly to corresponding PDSCH(s).

1. Specific DCI/MAC signaling (i.e., a TCI update command) may instructa set of a candidate TCI state (which may be indicated by PDSCHscheduling DCI including multi-TTI DCI) and an associated QCL assumptionto be changed to other values, and accordingly, the UE may apply thechanged update TCI state and associated QCL assumption set from a timepoint (i.e., TCI update timing) after a specific time from a receptiontime of the TCI update command or a corresponding ACK feedback time.

In the above situation, when the TCI update timing is located after thereception time of at least one of PDSCH-Ds, a non-updated TCI state andassociated QCL assumption set prior to the change may be applied to allPDSCH-Ds. When the TCI update timing is located before the receptiontimes of all PDSCH-Ds, the updated TCI state and associated QCLassumption set after the change may be applied to all PDSCH-Ds.

In another example, when the TCI update timing is located after thereception time of a specific one (some or all) of the PDSCH-Ds, the sameTCI state and associated QCL assumption as those of a PDSCH-C may beapplied to the specific PDSCH-D (by treating the specific PDSCH-D in thesame manner for the PDSCH-C for which the DCI-to-PDSCH time offset isless than the specific threshold), whereas the updated TCI state andassociated QCL assumption set after the change may be applied to theremaining PDSCH-Ds (for which the TCI update timing is located beforethe reception times of all PDSCH-Ds). When the TCI update timing islocated before the reception times of all PDSCH-Ds, the updated TCIstate and associated QCL assumption set after the change may be appliedto all PDSCH-Ds.

And/or, reception of a PDSCH located before the TCI update timing amongthe plurality of PDSCHs scheduled by the multi-TTI DCI may be dropped,and the PDSCH may be considered equally as the following invalid PDSCH.Alternatively, reception of a PDSCH located before the TCI update timingamong the plurality of PDSCH-Ds (scheduled by the multi-TTI DCI) may bedropped, and the PDSCH may be considered equally as the followinginvalid PDSCH.

2. In the above example, the first PDSCH may refer to the first ofactually transmitted valid PDSCHs except for invalid PDSCHs whichoverlap in time with a specific (e.g., semi-statically configured byhigher-layer signaling such as tdd-UL-DL-ConfigurationCommon ortdd-UL-DL-ConfigurationDedicated) UL symbol and thus the transmissionsof which are dropped, or the first of PDSCHs indicated by the multi-TTIDCI regardless of whether they are actually transmitted.

ii. Opt 2: When the DCI-to-PDSCH time offsets of all PDSCHs are equal toor greater than a specific threshold, all of the PDSCHs (i.e., PDSCH-Ds)may be received by applying a TCI state indicated by the DCI and anassociated QCL assumption. When the DCI-to-PDSCH time offset of at leastone PDSCH is less than the specific threshold, all scheduled PDSCHs(i.e., PDSCH-Cs) may be received by applying a TCI state configured for(reception of) a specific CORESET (e.g., a CORESET having a lowest ID)at a specific time (e.g., in the latest CORESET configuration slotincluding and/or before a transmission slot of the first of theplurality of PDSCHs) and an associated QCL assumption commonly to all ofthe PDSCHs.

1. In the above situation in which a TCI update command has beentransmitted/received, when a corresponding TCI update timing is locatedbefore the reception time of at least one of PDSCH-Ds, a non-updated TCIstate and associated QCL assumption set prior to the change may beapplied to all PDSCH-Ds. When the TCI update timing is located beforethe reception times of all PDSCH-Ds, the updated TCI state andassociated QCL assumption set after the change may be applied to allPDSCH-Ds.

In another example, when the TCI update timing is located after thereception time of a specific one (some or all) of the PDSCH-Ds, the sameTCI state and associated QCL assumption as those of a PDSCH-C may beapplied to the specific PDSCH-D (by treating the specific PDSCH-D in thesame manner as the PDSCH-C for which the DCI-to-PDSCH time offset isless than the specific threshold), whereas the updated TCI state andassociated QCL assumption set after the change may be applied to theremaining PDSCH-Ds (for which the TCI update timing is located beforethe reception times of all PDSCH-Ds). When the TCI update timing islocated before the reception times of all PDSCH-Ds, the updated TCIstate and associated QCL assumption set after the change may be appliedto all PDSCH-Ds.

Further in the above situation, a TCI state configured for (receptionof) a specific CORESET (e.g., a CORESET having a lowest ID) at aspecific time (e.g., in the latest CORESET configuration slot includingand/or before the first PDSCH transmission slot) and an associated QCLassumption may be commonly applied to all PDSCH-Cs, regardless ofwhether the TCI update timing is located after the reception time of atleast one of the PDSCH-Cs or before the reception times of all of thePDSCH-Cs.

And/or, reception of a PDSCH located before the TCI update timing amongthe plurality of PDSCHs scheduled by the multi-TTI DCI may be dropped,and the PDSCH may be considered equally as the following invalid PDSCH.Alternatively, reception of a PDSCH located before the TCI update timingamong a plurality of PDSCH-Ds (scheduled by the multi-TTI DCI) may bedropped, and the PDSCH may be considered equally as the followinginvalid PDSCH.

2. In the above example, all PDSCHs, at least one PDSCH, and the firstPDSCH may refer to all, at least one, and the first of actuallytransmitted valid PDSCHs except for invalid PDSCHs which overlap in timewith a specific (e.g., semi-statically configured by higher-layersignaling such as tdd-UL-DL-ConfigurationCommon ortdd-UL-DL-ConfigurationDedicated) UL symbol and thus the transmissionsof which are dropped, or all, at least one, and the first of PDSCHsindicated by the multi-TTI DCI regardless of whether they are actuallytransmitted.

iii. Opt 3: A PDSCH (i.e., PDSCH-D) for which a DCI-to-PDSCH time offsetis equal to or greater than a specific threshold may be received byapplying a TCI state indicated by the DCI and an associated QCLassumption, whereas a PDSCH (i.e., PDSCH-C) for which a DCI-to-PDSCHtime offset is less than the specific threshold may be received byapplying a TCI state configured for (reception of) a specific CORESET(e.g., a CORESET having a lowest ID) at a specific time (e.g., in thelatest CORESET configuration slot including and/or before the firstPDSCH transmission slot among a plurality of PDSCHs) and an associatedQCL assumption commonly to corresponding PDSCH(s).

1. In the above situation in which a TCI update command has beentransmitted/received, when a TCI update timing is located before thereception time of at least one of PDSCH-Ds, a non-updated TCI state andassociated QCL assumption set prior to the change may be applied to allPDSCH-Ds. When the TCI update timing is located before the receptiontimes of all PDSCH-Ds, the updated TCI state and associated QCLassumption set after the change may be applied to all PDSCH-Ds.

In another example, when the TCI update timing is located after thereception time of a specific one (some or all) of the PDSCH-Ds, the sameTCI state and associated QCL assumption as those of a PDSCH-C may beapplied to the specific PDSCH-D (by treating the specific PDSCH-D in thesame manner as the PDSCH-C for which the DCI-to-PDSCH time offset isless than the specific threshold), whereas the updated TCI state andassociated QCL assumption set after the change may be applied to theremaining PDSCH-Ds (for which the TCI update timing is located beforethe reception times of all PDSCH-Ds). When the TCI update timing islocated before the reception times of all PDSCH-Ds, the updated TCIstate and associated QCL assumption set after the change may be appliedto all PDSCH-Ds.

And/or, reception of a PDSCH located before the TCI update timing amongthe plurality of PDSCHs scheduled by the multi-TTI DCI may be dropped,and the PDSCH may be considered equally as the following invalid PDSCH.Alternatively, reception of a PDSCH located before the TCI update timingamong a plurality of PDSCH-Ds (scheduled by the multi-TTI DCI) may bedropped, and the PDSCH may be considered equally as the followinginvalid PDSCH.

iv. Opt 4: A different TCI state and associated QCL assumption for PDSCHreception may be applied according to an interval between PDSCHs and/oran SCS configured for a PDSCH. Specifically, for a PDSCH having aDCI-to-PDSCH time offset less than a specific threshold, or for allscheduled PDSCHs including at least one PDSCH having a DCI-to-PDSCH timeoffset less than the specific threshold, the following operations may beperformed.

1. For example, when PDSCHs are scheduled in consecutive symbols orconsecutive slots (or with a gap less than X symbols or Y slots betweenadjacent PDSCHs), the method of Opt 1 or Opt 2 may be applied. WhenPDSCHs are scheduled in non-consecutive symbols or non-consecutive slots(or with a gap equal to or greater than X symbols or Y slots betweenadjacent PDSCHs), the method of Opt 3 (or Opt 1) may be applied.

2. In another example, when a relatively large SCS (e.g., 480 KHz and960 KHz, or 960 KHz) is configured for PDSCHs, the method of Opt 1 orOpt 2 may be applied. When a relatively small SCS (e.g., 120 KHz, or 120KHz and 480 KHz) is configured for the PDSCHs, the method of Opt 3 (orOpt 1) may be applied.

3. In the above example, at least one PDSCH and a specific PDSCH mayrefer to at least one and a specific one of actually transmitted validPDSCHs except for invalid PDSCHs which overlap in time with a specific(e.g., semi-statically configured) UL symbol and the transmissions ofwhich are dropped, or at least one and a specific one of PDSCHsindicated by multi-TTI DCI regardless of whether the PDSCHs are actuallytransmitted.

C. When a PDCCH and a PDSCH overlap with each other in time, thefollowing operation may be performed conventionally.

i. When the QCL (type D) assumption is different between the PDCCH andthe PDSCH, the PDCCH may be received (while reception of the PDSCH maybe dropped).

D. Among a plurality of PDSCHs scheduled by multi-TTI DCI,

i. Opt A: When a PDSCH and a specific PDCCH between which a DCI-to-PDSCHtime offset is less than a specific threshold overlap with each other intime, and the QCL (type D) assumption is different between the PDSCH andthe PDCCH, the PDCCH may be received (while reception of the PDSCH maybe dropped). When a PDSCH and a specific PDCCH between which theDCI-to-PDSCH time offset is equal to or greater than the specificthreshold overlap with each other in time, and the QCL (type D)assumption is different between the PDSCH and the PDCCH, the PDSCH maybe received (while reception of the PDCCH may be dropped).

Alternatively, when a PDSCH for which application of a TCI stateconfigured for a specific CORESET and an associated QCL assumption isdetermined by Opt 1/2/3/4 (or any other method) and a specific PDCCHoverlap with each other in time, and the QCL (type D) assumption isdifferent between the PDSCH and the PDCCH, the PDCCH may be received(while reception of the PDSCH may be dropped). When a PDSCH for whichapplication of a TCI state indicated by DCI and an associated QCLassumption is determined and a specific PDCCH overlap with each other intime, and the QCL (type D) assumption is different between the PDSCH andthe PDCCH, the PDSCH may be received (while reception of the PDCCH maybe dropped).

ii. Opt B: In the case where it is determined to apply a TCI stateconfigured for a specific CORESET and an associated QCL assumption toall scheduled PDSCHs (when received) by Opt 1/2/3/4 (or any othermethod), when the QCL (type D) assumption is different between acorresponding PDSCH and a PDCCH (overlapping with the PDSCH in time),the PDSCH may be received (while reception of the PDCCH may be dropped).And/or, in the case where it is determined to apply a TCI stateconfigured for a specific CORESET and an associated QCL assumption tospecific some (or all) scheduled PDSCHs (when received) by Opt 1/2/3/4(or any other method), when the QCL (type D) assumption is differentbetween a corresponding PDSCH and a PDCCH (overlapping with the PDSCH intime), the PDCCH may be received (while reception of the PDSCH may bedropped).

Alternatively, in the case where it is determined to apply a TCI stateconfigured for a specific CORESET and an associated QCL assumption toall scheduled PDSCHs (when received) by Opt 1/2/3/4 (or any othermethod), when the QCL (type D) assumption is different between acorresponding PDSCH and a PDCCH (overlapping with the PDSCH in time),the PDCCH may be received (while reception of the PDSCH may be dropped).Otherwise (i.e., in the case where it is determined to apply a TCI stateindicated by DCI and an associated QCL assumption to at least one PDSCH(when received), when the QCL (type D) assumption is different between acorresponding PDSCH and a PDCCH (overlapping with the PDSCH in time)(for all scheduled PDSCHs), the PDSCH may be received (while receptionof the PDCCH may be dropped).

Alternatively, in the case where it is determined to apply a TCI stateindicated by DCI and an associated QCL assumption to all scheduledPDSCHs (when received) by Opt 1/2/3/4 (or any other method), when theQCL (type D) assumption is different between a corresponding PDSCH and aPDCCH (overlapping with the PDSCH in time), the PDSCH may be received(while reception of the PDCCH may be dropped). Otherwise (i.e., in thecase where it is determined to apply a TCI state configured for aspecific CORESET and an associated QCL assumption to at least one PDSCH(when received), when the QCL (type D) assumption is different between acorresponding PDSCH and a PDCCH (overlapping with the PDSCH in time)(for all scheduled PDSCHs), the PDCCH may be received (while receptionof the PDSCH may be dropped).

iii. Opt C: In the case where it is determined to apply a TCI stateconfigured for a specific CORESET and an associated QCL assumption tospecific some (or all of) scheduled PDSCHs (when received) by Opt1/2/3/4 (or any other method), when the QCL (type D) assumption isdifferent between a corresponding PDSCH and a PDCCH (overlapping withthe PDSCH in time), the PDSCH may be received (while reception of thePDCCH may be dropped). And/or in the case where it is determined toapply a TCI state indicated by DCI and an associated QCL assumption toall scheduled PDSCHs (when received) by Opt 1/2/3/4 (or any othermethod), when the QCL (type D) assumption is different between acorresponding PDSCH and a PDCCH (overlapping with the PDSCH in time),the PDCCH may be received (while reception of the PDSCH may be dropped).

Alternatively, in the case where it is determined to apply a TCI stateconfigured for a specific CORESET and an associated QCL assumption to atleast one PDSCH (when received) by Opt 1/2/3/4 (or any other method),when the QCL (type D) assumption is different between a correspondingPDSCH and a PDCCH (overlapping with the PDSCH in time) (for allscheduled PDSCHs), the PDCCH may be received (while reception of thePDSCH may be dropped).

Otherwise (in the case where it is determined to apply a TCI stateindicated by DCI and an associated QCL assumption to all scheduledPDSCHs (when received)), when the QCL (type D) assumption is differentbetween a corresponding PDSCH and a PDCCH (overlapping with the PDSCH intime), the PDSCH may be received (while reception of the PDCCH may bedropped).

Alternatively, in the case where it is determined to apply a TCI stateindicated by DCI and an associated QCL assumption to at least one PDSCH(when received) by Opt 1/2/3/4 (or any other method), when the QCL (typeD) assumption is different between a corresponding PDSCH and a PDCCH(overlapping with the PDSCH in time) (for all scheduled PDSCHs), thePDSCH may be received (while reception of the PDCCH may be dropped).Otherwise (in the case where it is determined to apply a TCI stateconfigured for a specific CORESET and an associated QCL assumption toall scheduled PDSCHs (when received)), when the QCL (type D) assumptionis different between a corresponding PDSCH and a PDCCH (overlapping withthe PDSCH in time), the PDCCH may be received (while reception of thePDSCH may be dropped).

iv. Opt D: In the case where a plurality of PDSCHs are scheduled bymulti-TTI DCI, when the QCL (type D) assumption is different between acorresponding PDSCH and a PDCCH (overlapping with the PDSCH in time),the PDSCH may be received (while reception of the PDCCH may be dropped).

Alternatively, in the case where a plurality of PDSCHs are scheduled bymulti-TTI DCI, when the QCL (type D) assumption is different between acorresponding PDSCH and a PDCCH (overlapping with the PDSCH in time),the PDCCH may be received (while reception of the PDSCH may be dropped).

1. In the above example, a plurality of PDSCHs refer to a plurality ofactually transmitted valid PDSCHs except for invalid PDSCHs whichoverlap in time with a specific (e.g., semi-statically configured) ULsymbol and the transmissions of which are skipped, or a plurality ofPDSCHs indicated by multi-TTI DCI regardless of whether they areactually transmitted.

E. A CORESET and a CORESET configuration slot used to determine a TCIstate and an associated QCL assumption which are applied to reception ofa specific PDSCH (e.g., the first or each of a plurality of PDSCHsscheduled by multi-TTI DCI) (e.g., PDSCH-x) may be replaced with aCORESET configured with the same CORSET pool index (e.g.,coresetPoolIndex) as a CORESET carrying a PDCCH that schedules thespecific PDSCH-X, and a slot in which the CORESET is configured, in asituation in which a PDSCH transmission based on a plurality of TRPs isconfigured.

F. Alternatively, in the case of a specific PDSCH (e.g., PDSCH-x)received by applying a TCI state configured for a specific CORSET and anassociated QCL assumption in the above example, the PDSCH-x may bereceived by applying a TCI state configured for a specific TCI codepoint(e.g., having a lowest index) and an associated QCL assumption, amongTCI codepoints (in a pair) configured with two (different) TCI statesamong TCI codepoints (configured for PDSCH reception) that may beindicated by DCI in a situation in which a PDSCH transmission based on aplurality of TRPs is configured.

G. Alternatively, in the case of a specific PDSCH (e.g., PDSCH-x)received by applying a TCI state configured for a specific CORSET and anassociated QCL assumption in the above example, the PDSCH-x may bereceived by applying a TCI state configured for a specific TCI codepoint(e.g., having a lowest index) and an associated QCL assumption, amongTCI codepoints (in a pair) configured with two (different) TCI statesamong (activated) TCI code points (configured for PDSCH reception) thatmay be indicated by DCI, in a situation in which a PDSCH transmission ina specific cell is scheduled by DCI in another cell (cross-CCscheduling).

Distinction is made between the above-described various DCI fieldconfiguration methods/options, for convenience of description. Aplurality of configuration methods/options may be combined, and each maybe implemented as an individual invention.

FIG. 10 illustrates multi-PDSCH scheduling and HARQ-ACK reportingaccording to an embodiment of the present disclosure. FIG. 10 isexemplary, not limiting the present disclosure.

A UE may receive information from a BS by higher-layer signaling (V320).For example, configuration information related to multi-PDSCH schedulingand configuration information related to multi-PDSCH HARQ-ACK feedbackmay be received by higher-layer signaling. For example, higher-layerparameters (or table) related to a value to be indicated by a state ofat least one of the afore-descried DCI fields may be configured.

The UE may receive DCI (one PDCCH signal) (V330). The UE may performblind detection for DCI that schedules multiple PDSCHs based on theinformation received by the higher-layer signaling.

The BS may transmit multiple PDSCHs scheduled by one DCI transmission(V335). The UE may receive the multiple PDSCHs based on the DCI. Forexample, the multiple PDSCHs may be received based on the state of atleast one field of the DCI.

The UE may generate/determine an HARQ-ACK for (all or at least part of)the received PDSCHs (V337). The HARQ-ACK may be generated based on aspecific codebook. The UE may refer to the higher-layer signaledinformation and/or the DCI to generate/determine the HARQ-ACK. Forexample, the HARQ-ACK may be generated based on a Type-1 codebook, aType-2 codebook, or a Type-3 codebook.

The UE may transmit the HARQ-ACK for the PDSCHs (V338). HARQ-ACKtransmission resources (time resources and a timing) may be determinedbased on the DCI and a (last) PDSCH.

FIG. 11 illustrates multi-PDSCH transmission/reception and HARQ-ACKreception according to an embodiment of the present disclosure. FIG. 11is exemplary, not limiting the present disclosure.

A UE may receive information from a BS by higher-layer signaling (B310).For example, configuration information related to multi-PUSCH schedulingand configuration information related to multi-PUSCH HARQ-ACK feedbackmay be received by higher-layer signaling. For example, high-layerparameters (or table) related to a value to be indicated by a state ofat least one of the afore-descried DCI fields may be configured.

The UE may transmit a scheduling request (SR) (B315). The SR may be aresource allocation request for multi-PUSCH transmission.

The UE may receive DCI (one PDCCH signal) (B320). The UE may performblind detection for DCI that schedules multiple PUSCHs based on theinformation received by the higher-layer signaling.

The UE may transmit multiple PUSCHs based on one DCI reception (B325).The BS may receive the multiple PUSCHs based on the DCI. For example,the multiple PUSCHs may be transmitted/received based on the state of atleast one field of the DCI.

The BS may generate/determine an HARQ-ACK for (all or at least part of)the received PUSCHs (B327).

The BS may transmit the HARQ-ACK for the PUSCHs (B330).

The UE may perform a retransmission based on the HARQ-ACK (B340).

FIG. 12 is a diagram illustrating a signal transmission/reception methodaccording to an embodiment of the disclosure. FIG. 12 relates toexemplary implementation of at least part of the afore-describedproposals of the present disclosure, and the present disclosure is notlimited to FIG. 12 .

Referring to FIG. 12 , a UE receives DCI scheduling a plurality ofPDSCHs (C05).

The UE performs PDSCH reception for at least part of the plurality ofPDSCHs based on the DCI (C10).

The UE determines a specific codebook-based HARQ-ACK, based on a resultof the PDSCH reception (C15).

The UE my transmit the HARQ-ACK in slot #N related to a specificcandidate PDSCH-to-HARQ feedback timing value (K1 value) indicated bythe DCI among a plurality of candidate K1 values configured for the UE(C20).

In determining the HARQ-ACK (C15), based on that a first-typecodebook-based HARQ-ACK is configured for the scheduling of theplurality of PDSCHs, the UE may perform first SLIV pruning based on acombination of SLIV values of PDSCHs which can be potentially scheduledin each slot of a bundling window determined based on the plurality ofcandidate K1 values, and perform second SLIV pruning based on acombination of SLIV values of PDSCHs which can be potentially scheduledin at least one slot not belonging to the bundling window.

First ACK/NACK sub-payload for each slot of the bundling window may bedetermined based on the first SLIV pruning.

Second ACK/NACK sub-payload for the at least one slot not belonging tothe bundling window may be determined based on the second SLIV pruning.

The UE may generate a total payload of the first-type codebook-basedHARQ-ACK by concatenating the first ACK/NACK sub-payload and the secondACK/NACK sub-payload, or arranging the first ACK/NACK sub-payload andthe second ACK/NACK sub-payload based on a time order of correspondingslots.

The at least one slot not belonging to the bundling window, for whichthe second SLIV pruning is performed, may be located before the bundlingwindow in a time domain.

The at least one slot not belonging to the bundling window, for whichthe second SLIV pruning is performed, may be a slot in which a PDSCHlocated outside the bundling window among the plurality of PDSCHs isreceived.

A TDRA field included in the DCI may indicate one row of a TDRA tableconfigured for the UE.

At least one row of the TDRA table may include a plurality of {K0, PDSCHmapping type, SLIV} parameter sets, where ‘K0’ may indicate a physicaldownlink control channel (PDCCH)-to-PDSCH slot offset.

The at least one slot not belonging to the bundling window, for whichthe second SLIV pruning is performed, may be determined based on ‘K0’included in a parameter set that does not correspond to a last slot ineach row of the TDRA table.

The bundling window for which the first SLIV pruning is performed isdetermined by combining the plurality of candidate K1 values with aparameter set corresponding to the last slot in each row of the TDRAtable.

For example, on the assumption that P {K0, PDSCH mapping type, SLIV}parameter sets are included in a specific row of the TDRA table andcorrespond to a total of S slots (e.g., P PDSCHs scheduled based on thespecific row are mapped to a total of S slots), S=P or S<P (i.e., S≤P)depending on the configuration of each row.

The HARQ-ACK is generated for a valid PDSCH except for an invalid PDSCHoverlapping with a UL symbol configured by higher-layer signaling, amongthe plurality of PDSCHs.

The UE may perform each of the first SLIV pruning and the second SLIVpruning while excluding an invalid PDSCH overlapping with a UL symbolconfigured by higher-layer signaling.

In the process of determining the HARQ-ACK (C15), HARQ process IDs maybe consecutively/sequentially assigned to valid PDSCHs.

FIG. 13 is a diagram illustrating HARQ process ID allocation accordingto an embodiment of the present disclosure. FIG. 13 relates to exemplaryimplementation of the afore-described proposals of the presentdisclosure, and the present disclosure is not limited to FIG. 13 .

Referring to FIG. 13 , the UE may receive information indicating a UL/DLresource configuration by higher-layer signaling (D05); receive DCI thatschedules a plurality of PDSCHs (D10); perform PDSCH reception for atleast part of the plurality of PDSCHs based on the DCI (D15); andperform an HARQ process for each PDSCH based on a result of the PDSCHreception (D20). The HARQ process may include A/N determination andHARQ-ACK payload generation, HARQ-ACK reporting, and retransmissionreception on the side of the UE, and may include HARQ-ACK reception andretransmission on the side of a BS.

The UE may determine a PDSCH overlapping with a UL symbol configured bythe information indicating the UL/DL resource configuration among theplurality of PDSCHs to be an invalid PDSCH.

When performing the HARQ process for each PDSCH, the UE mayconsecutively or sequentially HARQ process IDs only to valid PDSCHsexcept for invalid PDSCHs.

Based on an HARQ process ID indicated by the DCI being #n, and thenumber of valid PDSCHs among the plurality of PDSCHs being k, the UE mayallocate HARQ process ID #n, HARQ process ID #n+1, HARQ process ID #n+2,. . . , HARQ process ID #n+k−1 to k valid PDSCHs, respectively.

FIG. 14 illustrates a communication system 1 applied to the presentdisclosure.

Referring to FIG. 14 , a communication system 1 applied to the presentdisclosure includes wireless devices, Base Stations (BSs), and anetwork. Herein, the wireless devices represent devices performingcommunication using Radio Access Technology (RAT) (e.g., 5G New RAT(NR)) or Long-Term Evolution (LTE)) and may be referred to ascommunication/radio/5G devices. The wireless devices may include,without being limited to, a robot 100 a, vehicles 100 b-1 and 100 b-2,an eXtended Reality (XR) device 100 c, a hand-held device 100 d, a homeappliance 100 e, an Internet of Things (IoT) device 100 f, and anArtificial Intelligence (AI) device/server 400. For example, thevehicles may include a vehicle having a wireless communication function,an autonomous driving vehicle, and a vehicle capable of performingcommunication between vehicles. Herein, the vehicles may include anUnmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may includean Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) deviceand may be implemented in the form of a Head-Mounted Device (HMD), aHead-Up Display (HUD) mounted in a vehicle, a television, a smartphone,a computer, a wearable device, a home appliance device, a digitalsignage, a vehicle, a robot, etc. The hand-held device may include asmartphone, a smartpad, a wearable device (e.g., a smartwatch or asmartglasses), and a computer (e.g., a notebook). The home appliance mayinclude a TV, a refrigerator, and a washing machine. The IoT device mayinclude a sensor and a smartmeter. For example, the BSs and the networkmay be implemented as wireless devices and a specific wireless device200 a may operate as a BS/network node with respect to other wirelessdevices.

The wireless devices 100 a to 100 f may be connected to the network 300via the BSs 200. An AI technology may be applied to the wireless devices100 a to 100 f and the wireless devices 100 a to 100 f may be connectedto the AI server 400 via the network 300. The network 300 may beconfigured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g.,NR) network. Although the wireless devices 100 a to 100 f maycommunicate with each other through the BSs 200/network 300, thewireless devices 100 a to 100 f may perform direct communication (e.g.,sidelink communication) with each other without passing through theBSs/network. For example, the vehicles 100 b-1 and 100 b-2 may performdirect communication (e.g. Vehicle-to-Vehicle(V2V)/Vehicle-to-everything (V2X) communication). The IoT device (e.g.,a sensor) may perform direct communication with other IoT devices (e.g.,sensors) or other wireless devices 100 a to 100 f.

Wireless communication/connections 150 a, 150 b, or 150 c may beestablished between the wireless devices 100 a to 100 f/BS 200, or BS200/BS 200. Herein, the wireless communication/connections may beestablished through various RATs (e.g., 5G NR) such as uplink/downlinkcommunication 150 a, sidelink communication 150 b (or, D2Dcommunication), or inter BS communication (e.g. relay, Integrated AccessBackhaul (IAB)). The wireless devices and the BSs/the wireless devicesmay transmit/receive radio signals to/from each other through thewireless communication/connections 150 a and 150 b. For example, thewireless communication/connections 150 a and 150 b may transmit/receivesignals through various physical channels. To this end, at least a partof various configuration information configuring processes, varioussignal processing processes (e.g., channel encoding/decoding,modulation/demodulation, and resource mapping/demapping), and resourceallocating processes, for transmitting/receiving radio signals, may beperformed based on the various proposals of the present disclosure.

FIG. 15 illustrates wireless devices applicable to the presentdisclosure.

Referring to FIG. 15 , a first wireless device 100 and a second wirelessdevice 200 may transmit radio signals through a variety of RATs (e.g.,LTE and NR). Herein, {the first wireless device 100 and the secondwireless device 200} may correspond to {the wireless device 100 x andthe BS 200} and/or {the wireless device 100 x and the wireless device100 x} of FIG. 14 .

The first wireless device 100 may include one or more processors 102 andone or more memories 104 and additionally further include one or moretransceivers 106 and/or one or more antennas 108. The processor(s) 102may control the memory(s) 104 and/or the transceiver(s) 106 and may beconfigured to implement the descriptions, functions, procedures,proposals, methods, and/or operational flowcharts disclosed in thisdocument. For example, the processor(s) 102 may process informationwithin the memory(s) 104 to generate first information/signals and thentransmit radio signals including the first information/signals throughthe transceiver(s) 106. The processor(s) 102 may receive radio signalsincluding second information/signals through the transceiver 106 andthen store information obtained by processing the secondinformation/signals in the memory(s) 104. The memory(s) 104 may beconnected to the processor(s) 102 and may store a variety of informationrelated to operations of the processor(s) 102. For example, thememory(s) 104 may store software code including commands for performinga part or the entirety of processes controlled by the processor(s) 102or for performing the descriptions, functions, procedures, proposals,methods, and/or operational flowcharts disclosed in this document.Herein, the processor(s) 102 and the memory(s) 104 may be a part of acommunication modem/circuit/chip designed to implement RAT (e.g., LTE orNR). The transceiver(s) 106 may be connected to the processor(s) 102 andtransmit and/or receive radio signals through one or more antennas 108.Each of the transceiver(s) 106 may include a transmitter and/or areceiver. The transceiver(s) 106 may be interchangeably used with RadioFrequency (RF) unit(s). In the present disclosure, the wireless devicemay represent a communication modem/circuit/chip.

The second wireless device 200 may include one or more processors 202and one or more memories 204 and additionally further include one ormore transceivers 206 and/or one or more antennas 208. The processor(s)202 may control the memory(s) 204 and/or the transceiver(s) 206 and maybe configured to implement the descriptions, functions, procedures,proposals, methods, and/or operational flowcharts disclosed in thisdocument. For example, the processor(s) 202 may process informationwithin the memory(s) 204 to generate third information/signals and thentransmit radio signals including the third information/signals throughthe transceiver(s) 206. The processor(s) 202 may receive radio signalsincluding fourth information/signals through the transceiver(s) 106 andthen store information obtained by processing the fourthinformation/signals in the memory(s) 204. The memory(s) 204 may beconnected to the processor(s) 202 and may store a variety of informationrelated to operations of the processor(s) 202. For example, thememory(s) 204 may store software code including commands for performinga part or the entirety of processes controlled by the processor(s) 202or for performing the descriptions, functions, procedures, proposals,methods, and/or operational flowcharts disclosed in this document.Herein, the processor(s) 202 and the memory(s) 204 may be a part of acommunication modem/circuit/chip designed to implement RAT (e.g., LTE orNR). The transceiver(s) 206 may be connected to the processor(s) 202 andtransmit and/or receive radio signals through one or more antennas 208.Each of the transceiver(s) 206 may include a transmitter and/or areceiver. The transceiver(s) 206 may be interchangeably used with RFunit(s). In the present disclosure, the wireless device may represent acommunication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices 100 and 200 willbe described more specifically. One or more protocol layers may beimplemented by, without being limited to, one or more processors 102 and202. For example, the one or more processors 102 and 202 may implementone or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP,RRC, and SDAP). The one or more processors 102 and 202 may generate oneor more Protocol Data Units (PDUs) and/or one or more Service Data Unit(SDUs) according to the descriptions, functions, procedures, proposals,methods, and/or operational flowcharts disclosed in this document. Theone or more processors 102 and 202 may generate messages, controlinformation, data, or information according to the descriptions,functions, procedures, proposals, methods, and/or operational flowchartsdisclosed in this document. The one or more processors 102 and 202 maygenerate signals (e.g., baseband signals) including PDUs, SDUs,messages, control information, data, or information according to thedescriptions, functions, procedures, proposals, methods, and/oroperational flowcharts disclosed in this document and provide thegenerated signals to the one or more transceivers 106 and 206. The oneor more processors 102 and 202 may receive the signals (e.g., basebandsignals) from the one or more transceivers 106 and 206 and acquire thePDUs, SDUs, messages, control information, data, or informationaccording to the descriptions, functions, procedures, proposals,methods, and/or operational flowcharts disclosed in this document.

The one or more processors 102 and 202 may be referred to ascontrollers, microcontrollers, microprocessors, or microcomputers. Theone or more processors 102 and 202 may be implemented by hardware,firmware, software, or a combination thereof. As an example, one or moreApplication Specific Integrated Circuits (ASICs), one or more DigitalSignal Processors (DSPs), one or more Digital Signal Processing Devices(DSPDs), one or more Programmable Logic Devices (PLDs), or one or moreField Programmable Gate Arrays (FPGAs) may be included in the one ormore processors 102 and 202. The descriptions, functions, procedures,proposals, methods, and/or operational flowcharts disclosed in thisdocument may be implemented using firmware or software and the firmwareor software may be configured to include the modules, procedures, orfunctions. Firmware or software configured to perform the descriptions,functions, procedures, proposals, methods, and/or operational flowchartsdisclosed in this document may be included in the one or more processors102 and 202 or stored in the one or more memories 104 and 204 so as tobe driven by the one or more processors 102 and 202. The descriptions,functions, procedures, proposals, methods, and/or operational flowchartsdisclosed in this document may be implemented using firmware or softwarein the form of code, commands, and/or a set of commands.

The one or more memories 104 and 204 may be connected to the one or moreprocessors 102 and 202 and store various types of data, signals,messages, information, programs, code, instructions, and/or commands.The one or more memories 104 and 204 may be configured by Read-OnlyMemories (ROMs), Random Access Memories (RAMs), Electrically ErasableProgrammable Read-Only Memories (EPROMs), flash memories, hard drives,registers, cash memories, computer-readable storage media, and/orcombinations thereof. The one or more memories 104 and 204 may belocated at the interior and/or exterior of the one or more processors102 and 202. The one or more memories 104 and 204 may be connected tothe one or more processors 102 and 202 through various technologies suchas wired or wireless connection.

The one or more transceivers 106 and 206 may transmit user data, controlinformation, and/or radio signals/channels, mentioned in the methodsand/or operational flowcharts of this document, to one or more otherdevices. The one or more transceivers 106 and 206 may receive user data,control information, and/or radio signals/channels, mentioned in thedescriptions, functions, procedures, proposals, methods, and/oroperational flowcharts disclosed in this document, from one or moreother devices. For example, the one or more transceivers 106 and 206 maybe connected to the one or more processors 102 and 202 and transmit andreceive radio signals. For example, the one or more processors 102 and202 may perform control so that the one or more transceivers 106 and 206may transmit user data, control information, or radio signals to one ormore other devices. The one or more processors 102 and 202 may performcontrol so that the one or more transceivers 106 and 206 may receiveuser data, control information, or radio signals from one or more otherdevices. The one or more transceivers 106 and 206 may be connected tothe one or more antennas 108 and 208 and the one or more transceivers106 and 206 may be configured to transmit and receive user data, controlinformation, and/or radio signals/channels, mentioned in thedescriptions, functions, procedures, proposals, methods, and/oroperational flowcharts disclosed in this document, through the one ormore antennas 108 and 208. In this document, the one or more antennasmay be a plurality of physical antennas or a plurality of logicalantennas (e.g., antenna ports). The one or more transceivers 106 and 206may convert received radio signals/channels etc. from RF band signalsinto baseband signals in order to process received user data, controlinformation, radio signals/channels, etc. using the one or moreprocessors 102 and 202. The one or more transceivers 106 and 206 mayconvert the user data, control information, radio signals/channels, etc.processed using the one or more processors 102 and 202 from the baseband signals into the RF band signals. To this end, the one or moretransceivers 106 and 206 may include (analog) oscillators and/orfilters.

FIG. 16 illustrates another example of a wireless device applied to thepresent disclosure. The wireless device may be implemented in variousforms according to a use-case/service (refer to FIG. 14 ).

Referring to FIG. 16 , wireless devices 100 and 200 may correspond tothe wireless devices 100 and 200 of FIG. 15 and may be configured byvarious elements, components, units/portions, and/or modules. Forexample, each of the wireless devices 100 and 200 may include acommunication unit 110, a control unit 120, a memory unit 130, andadditional components 140. The communication unit may include acommunication circuit 112 and transceiver(s) 114. For example, thecommunication circuit 112 may include the one or more processors 102 and202 and/or the one or more memories 104 and 204 of FIG. 15 . Forexample, the transceiver(s) 114 may include the one or more transceivers106 and 206 and/or the one or more antennas 108 and 208 of FIG. 15 . Thecontrol unit 120 is electrically connected to the communication unit110, the memory 130, and the additional components 140 and controlsoverall operation of the wireless devices. For example, the control unit120 may control an electric/mechanical operation of the wireless devicebased on programs/code/commands/information stored in the memory unit130. The control unit 120 may transmit the information stored in thememory unit 130 to the exterior (e.g., other communication devices) viathe communication unit 110 through a wireless/wired interface or store,in the memory unit 130, information received through the wireless/wiredinterface from the exterior (e.g., other communication devices) via thecommunication unit 110.

The additional components 140 may be variously configured according totypes of wireless devices. For example, the additional components 140may include at least one of a power unit/battery, input/output (I/O)unit, a driving unit, and a computing unit. The wireless device may beimplemented in the form of, without being limited to, the robot (100 aof FIG. 14 ), the vehicles (100 b-1 and 100 b-2 of FIG. 14 ), the XRdevice (100 c of FIG. 14 ), the hand-held device (100 d of FIG. 14 ),the home appliance (100 e of FIG. 14 ), the IoT device (100 f of FIG. 14), a digital broadcast terminal, a hologram device, a public safetydevice, an MTC device, a medicine device, a fintech device (or a financedevice), a security device, a climate/environment device, the AIserver/device (400 of FIG. 14 ), the BSs (200 of FIG. 14 ), a networknode, etc. The wireless device may be used in a mobile or fixed placeaccording to a use-example/service.

In FIG. 16 , the entirety of the various elements, components,units/portions, and/or modules in the wireless devices 100 and 200 maybe connected to each other through a wired interface or at least a partthereof may be wirelessly connected through the communication unit 110.For example, in each of the wireless devices 100 and 200, the controlunit 120 and the communication unit 110 may be connected by wire and thecontrol unit 120 and first units (e.g., 130 and 140) may be wirelesslyconnected through the communication unit 110. Each element, component,unit/portion, and/or module within the wireless devices 100 and 200 mayfurther include one or more elements. For example, the control unit 120may be configured by a set of one or more processors. As an example, thecontrol unit 120 may be configured by a set of a communication controlprocessor, an application processor, an Electronic Control Unit (ECU), agraphical processing unit, and a memory control processor. As anotherexample, the memory 130 may be configured by a Random Access Memory(RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM)), a flash memory,a volatile memory, a non-volatile memory, and/or a combination thereof.

FIG. 17 illustrates a vehicle or an autonomous driving vehicle appliedto the present disclosure. The vehicle or autonomous driving vehicle maybe implemented by a mobile robot, a car, a train, a manned/unmannedAerial Vehicle (AV), a ship, etc.

Referring to FIG. 17 , a vehicle or autonomous driving vehicle 100 mayinclude an antenna unit 108, a communication unit 110, a control unit120, a driving unit 140 a, a power supply unit 140 b, a sensor unit 140c, and an autonomous driving unit 140 d. The antenna unit 108 may beconfigured as a part of the communication unit 110. The blocks110/130/140 a to 140 d correspond to the blocks 110/130/140 of FIG. 16 ,respectively.

The communication unit 110 may transmit and receive signals (e.g., dataand control signals) to and from external devices such as othervehicles, BSs (e.g., gNBs and road side units), and servers. The controlunit 120 may perform various operations by controlling elements of thevehicle or the autonomous driving vehicle 100. The control unit 120 mayinclude an Electronic Control Unit (ECU). The driving unit 140 a maycause the vehicle or the autonomous driving vehicle 100 to drive on aroad. The driving unit 140 a may include an engine, a motor, apowertrain, a wheel, a brake, a steering device, etc. The power supplyunit 140 b may supply power to the vehicle or the autonomous drivingvehicle 100 and include a wired/wireless charging circuit, a battery,etc. The sensor unit 140 c may acquire a vehicle state, ambientenvironment information, user information, etc. The sensor unit 140 cmay include an Inertial Measurement Unit (IMU) sensor, a collisionsensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor,a heading sensor, a position module, a vehicle forward/backward sensor,a battery sensor, a fuel sensor, a tire sensor, a steering sensor, atemperature sensor, a humidity sensor, an ultrasonic sensor, anillumination sensor, a pedal position sensor, etc. The autonomousdriving unit 140 d may implement technology for maintaining a lane onwhich a vehicle is driving, technology for automatically adjustingspeed, such as adaptive cruise control, technology for autonomouslydriving along a determined path, technology for driving by automaticallysetting a path if a destination is set, and the like.

For example, the communication unit 110 may receive map data, trafficinformation data, etc. from an external server. The autonomous drivingunit 140 d may generate an autonomous driving path and a driving planfrom the obtained data. The control unit 120 may control the drivingunit 140 a such that the vehicle or the autonomous driving vehicle 100may move along the autonomous driving path according to the driving plan(e.g., speed/direction control). In the middle of autonomous driving,the communication unit 110 may aperiodically/periodically acquire recenttraffic information data from the external server and acquiresurrounding traffic information data from neighboring vehicles. In themiddle of autonomous driving, the sensor unit 140 c may obtain a vehiclestate and/or surrounding environment information. The autonomous drivingunit 140 d may update the autonomous driving path and the driving planbased on the newly obtained data/information. The communication unit 110may transfer information about a vehicle position, the autonomousdriving path, and/or the driving plan to the external server. Theexternal server may predict traffic information data using AItechnology, etc., based on the information collected from vehicles orautonomous driving vehicles and provide the predicted trafficinformation data to the vehicles or the autonomous driving vehicles.

FIG. 18 is a diagram illustrating a DRX operation of a UE according toan embodiment of the present disclosure.

The UE may perform a DRX operation in the afore-described/proposedprocedures and/or methods. A UE configured with DRX may reduce powerconsumption by receiving a DL signal discontinuously. DRX may beperformed in an RRC_IDLE state, an RRC_INACTIVE state, and anRRC_CONNECTED state. The UE performs DRX to receive a paging signaldiscontinuously in the RRC_IDLE state and the RRC_INACTIVE state. DRX inthe RRC_CONNECTED state (RRC_CONNECTED DRX) will be described below.

Referring to FIG. 18 , a DRX cycle includes an On Duration and anOpportunity for DRX. The DRX cycle defines a time interval betweenperiodic repetitions of the On Duration. The On Duration is a timeperiod during which the UE monitors a PDCCH. When the UE is configuredwith DRX, the UE performs PDCCH monitoring during the On Duration. Whenthe UE successfully detects a PDCCH during the PDCCH monitoring, the UEstarts an inactivity timer and is kept awake. On the contrary, when theUE fails in detecting any PDCCH during the PDCCH monitoring, the UEtransitions to a sleep state after the On Duration. Accordingly, whenDRX is configured, PDCCH monitoring/reception may be performeddiscontinuously in the time domain in the afore-described/proposedprocedures and/or methods. For example, when DRX is configured, PDCCHreception occasions (e.g., slots with PDCCH SSs) may be configureddiscontinuously according to a DRX configuration in the presentdisclosure. On the contrary, when DRX is not configured, PDCCHmonitoring/reception may be performed continuously in the time domain.For example, when DRX is not configured, PDCCH reception occasions(e.g., slots with PDCCH SSs) may be configured continuously in thepresent disclosure. Irrespective of whether DRX is configured, PDCCHmonitoring may be restricted during a time period configured as ameasurement gap.

Table 6 describes a DRX operation of a UE (in the RRC_CONNECTED state).Referring to Table 6, DRX configuration information is received byhigher-layer signaling (e.g., RRC signaling), and DRX ON/OFF iscontrolled by a DRX command from the MAC layer. Once DRX is configured,the UE may perform PDCCH monitoring discontinuously in performing theafore-described/proposed procedures and/or methods.

TABLE 6 Type of signals UE procedure 1^(st) step RRC signalling ReceiveDRX configuration (MAC- information CellGroupConfig) 2^(nd) Step MAC CEReceive DRX command ((Long) DRX command MAC CE) 3^(rd) Step — Monitor aPDCCH during an on-duration of a DRX cycle

MAC-CellGroupConfig includes configuration information required toconfigure MAC parameters for a cell group. MAC-CellGroupConfig may alsoinclude DRX configuration information. For example, MAC-CellGroupConfigmay include the following information in defining DRX.

Value of drx-OnDurationTimer: defines the duration of the startingperiod of the DRX cycle.

Value of drx-InactivityTimer: defines the duration of a time periodduring which the UE is awake after a PDCCH occasion in which a PDCCHindicating initial UL or DL data has been detected

Value of drx-HARQ-RTT-TimerDL: defines the duration of a maximum timeperiod until a DL retransmission is received after reception of a DLinitial transmission.

Value of drx-HARQ-RTT-TimerDL: defines the duration of a maximum timeperiod until a grant for a UL retransmission is received after receptionof a grant for a UL initial transmission.

drx-LongCycleStartOffset: defines the duration and starting time of aDRX cycle.

drx-ShortCycle (optional): defines the duration of a short DRX cycle.

When any of drx-OnDurationTimer, drx-InactivityTimer,drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is running, the UEperforms PDCCH monitoring in each PDCCH occasion, staying in the awakestate.

The above-described embodiments correspond to combinations of elementsand features of the present disclosure in prescribed forms. And, therespective elements or features may be considered as selective unlessthey are explicitly mentioned. Each of the elements or features can beimplemented in a form failing to be combined with other elements orfeatures. Moreover, it is able to implement an embodiment of the presentdisclosure by combining elements and/or features together in part. Asequence of operations explained for each embodiment of the presentdisclosure can be modified. Some configurations or features of oneembodiment can be included in another embodiment or can be substitutedfor corresponding configurations or features of another embodiment. And,it is apparently understandable that an embodiment is configured bycombining claims failing to have relation of explicit citation in theappended claims together or can be included as new claims by amendmentafter filing an application.

Those skilled in the art will appreciate that the present disclosure maybe carried out in other specific ways than those set forth hereinwithout departing from the spirit and essential characteristics of thepresent disclosure. The above embodiments are therefore to be construedin all aspects as illustrative and not restrictive. The scope of thedisclosure should be determined by the appended claims and their legalequivalents, not by the above description, and all changes coming withinthe meaning and equivalency range of the appended claims are intended tobe embraced therein.

INDUSTRIAL APPLICABILITY

The present disclosure is applicable to UEs, BSs, or other apparatusesin a wireless mobile communication system.

1-15. (canceled)
 16. A method of receiving a signal by a user equipment(UE) in a wireless communication system, the method comprising:receiving downlink control information (DCI) for scheduling a pluralityof physical downlink shared channels (PDSCHs); performing a PDSCHreception for the plurality of PDSCHs in PDSCH occasions related to theDCI; determining a hybrid automatic repeat request (HARD)-acknowledgment(ACK) for a set of PDSCH occasions including the PDSCH occasions relatedto the DCI, based on that Type-1 HARQ-ACK codebook is configured; andtransmitting the HARQ-ACK in a slot associated with a K1 value indicatedby the DCI from among K1 values which are PDSCH-to-HARQ feedback timingvalues configured in the UE through higher layer signaling, wherein theUE determines the set of PDSCH occasions to include: i) first PDSCHoccasions that can be scheduled in first slots associated with the K1values configured through the higher layer signaling, and ii) secondPDSCH occasions that can be scheduled in at least one second slotdetermined based on at least one K0 value which is a PDCCH-to-PDSCH slotoffset.
 17. The method of claim 16, wherein first ACK/negative-ACK(NACK) sub-payload for each of the first slots is determined based onthe first PDSCH occasions, and wherein second ACK/NACK sub-payload forthe at least one second slot is determined based on the second PDSCHoccasions.
 18. The method of claim 17, wherein the UE generates a totalpayload of the Type-1 HARQ-ACK codebook by concatenating the firstACK/NACK sub-payload and the second ACK/NACK sub-payload, or arrangingthe first ACK/NACK sub-payload and the second ACK/NACK sub-payload basedon a time order of corresponding slots.
 19. The method of claim 16,wherein the at least one second slot is located before the first slotsin a time domain.
 20. The method of claim 16, wherein the at least onesecond slot is determined from among slots other than the first slots.21. The method of claim 16, wherein a time domain resource allocation(TDRA) field included in the DCI indicates one row of a TDRA tableconfigured for the UE, and wherein at least one row of the TDRA tableincludes a plurality of {K0, PDSCH mapping type, start symbol and lengthindicator value (SLIV)} parameter sets.
 22. The method of claim 21,wherein the at least one second slot is determined based on ‘K0’included in a parameter set that does not correspond to a last slot ineach row of the TDRA table.
 23. The method of claim 21, wherein thefirst slots are determined by combining the K1 values configured throughhigher layer signaling with a parameter set corresponding to the lastslot in each row of the TDRA table.
 24. The method of claim 16, whereinthe HARQ-ACK is generated for a valid PDSCH except for an invalid PDSCHoverlapping with an uplink (UL) symbol configured by higher-layersignaling, among the plurality of PDSCHs.
 25. The method of claim 16,wherein the UE determines the first PDSCH occasions and the second PDSCHoccasions while excluding an invalid PDSCH overlapping with a UL symbolconfigured by higher-layer signaling.
 26. The method of claim 16,wherein at least one of the PDSCH occasions related to the DCI belongsto the first PDSCH occasions, and remaining of the PDSCH occasionsrelated to the DCI belong to the second PDSCH occasions.
 27. Acomputer-readable recording medium recording a program for performingthe method according to claim
 16. 28. A device for wirelesscommunication, the device comprising: a processor; and a memoryconfigured to store instructions that, when executed by the processor,perform operations comprising: receiving downlink control information(DCI) for scheduling a plurality of physical downlink shared channels(PDSCHs); performing a PDSCH reception for the plurality of PDSCHs inPDSCH occasions related to the DCI; determining a hybrid automaticrepeat request (HARD)-acknowledgment (ACK) for a set of PDSCH occasionsincluding the PDSCH occasions related to the DCI, based on that Type-1HARQ-ACK codebook is configured; and transmitting the HARQ-ACK in a slotassociated with a K1 value indicated by the DCI from among K1 valueswhich are PDSCH-to-HARQ feedback timing values configured in the devicethrough higher layer signaling, wherein the device determines the set ofPDSCH occasions to include: i) first PDSCH occasions that can bescheduled in first slots associated with the K1 values configuredthrough the higher layer signaling, and ii) second PDSCH occasions thatcan be scheduled in at least one second slot determined based on atleast one K0 value which is a PDCCH-to-PDSCH slot offset.
 29. The deviceaccording to claim 28, further comprising: a transceiver configured totransmit or receive a wireless signal under control of the processor,wherein the device is a 3rd generation partnership project (3GPP)-baseduser equipment (UE).
 30. A method of transmitting a signal by a basestation (BS) in a wireless communication system, the method comprising:transmitting downlink control information (DCI) for scheduling aplurality of physical downlink shared channels (PDSCHs); performing aPDSCH transmission for the plurality of PDSCHs in PDSCH occasionsrelated to the DCI; receiving a hybrid automatic repeat request(HARD)-acknowledgment (ACK) in a slot associated with a K1 valueindicated by the DCI from among K1 values which are PDSCH-to-HARQfeedback timing values configured in a user equipment (UE) by the BSthrough higher layer signaling; and determining a PDSCH to beretransmitted by processing the received HARQ-ACK, wherein in theprocessing of the received HARQ-ACK, the BS determines a set of PDSCHoccasions including the PDSCH occasions related to the DCI, based onthat Type-1 HARQ-ACK codebook is configured in the UE, and wherein theset of PDSCH occasions include: i) first PDSCH occasions that can bescheduled in first slots associated with the K1 values configuredthrough the higher layer signaling, and ii) second PDSCH occasions thatcan be scheduled in at least one second slot determined based on atleast one K0 value which is a PDCCH-to-PDSCH slot offset.
 31. A basestation (BS) for wireless communication, the BS comprising: a processor;and a memory configured to store instructions that, when executed by theprocessor, perform operations comprising: transmitting downlink controlinformation (DCI) for scheduling a plurality of physical downlink sharedchannels (PDSCHs); performing a PDSCH transmission for the plurality ofPDSCHs in PDSCH occasions related to the DCI; receiving a hybridautomatic repeat request (HARD)-acknowledgment (ACK) in a slotassociated with K1 value indicated by the DCI from among K1 values whichare PDSCH-to-HARQ feedback timing values configured in a user equipment(UE) by the BS through higher layer signaling; and determining a PDSCHto be retransmitted by processing the received HARQ-ACK, wherein in theprocessing of the received HARQ-ACK, the BS determines a set of PDSCHoccasions including the PDSCH occasions related to the DCI, based onthat Type-1 HARQ-ACK codebook is configured in the UE, and wherein theset of PDSCH occasions include: i) first PDSCH occasions that can bescheduled in first slots associated with the K1 values configuredthrough the higher layer signaling, and ii) second PDSCH occasions thatcan be scheduled in at least one second slot determined based on atleast one K0 value which is a PDCCH-to-PDSCH slot offset.